identity_resolve_batch

When to use it

Use identity_resolve_batch to resolve identity observations in a batch. On the workspace endpoint, pass projectId from project_list. On a project-scoped endpoint, the project is already bound: omit that argument and use the schema discovered from that endpoint.

Arguments

View the complete input schema, including nested contracts and alternative shapes. The schema is extracted from the workspace server’s Zod definitions. Runtime validation also enforces custom checks that JSON Schema cannot express.

Response shape

The implementation constructs payloads using these fields: count, results. The returned fields depend on the execution path.

MCP returns a text block containing the JSON operation result and a structuredContent copy. The envelope includes data, completeness, truncated, freshness, and warnings. Depending on the operation it can also include nextCursor, evidence, job, or receipt.

Check those fields before treating a conversational summary as the result. When a job is returned, inspect its status with the appropriate execution tool; a queued response is not confirmation that work finished. Follow evidence links when checking the underlying records.

Input methods

This request illustrates the argument structure. Replace every angle-bracket placeholder with a real value and supply any applicable optional fields from the schema. Nested business contracts must match your actual configuration. Send it through an authenticated, initialized MCP client; this JSON alone does not establish a session or sign you in.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "identity_resolve_batch",
    "arguments": {
      "observations": [
        {
          "operationKey": "<OPERATION_KEY>",
          "ontologyPackageId": "<ONTOLOGY_PACKAGE_ID_UUID>",
          "entityId": "<ENTITY_ID>",
          "typeRef": "<TYPE_REF>",
          "sourceNamespace": "<SOURCE_NAMESPACE>",
          "sourceKey": "<SOURCE_KEY>",
          "sourceId": "<SOURCE_ID>",
          "validFrom": "<VALID_FROM>",
          "validTo": "<VALID_TO>",
          "names": [
            "<NAMES>"
          ],
          "attributes": {},
          "evidence": [
            {
              "reference": "<REFERENCE>",
              "description": "<DESCRIPTION>"
            }
          ]
        }
      ],
      "idempotencyKey": "<UNIQUE_KEY_FOR_THIS_OPERATION>",
      "projectId": "<PROJECT_ID_UUID>"
    }
  }
}

FAQ

What access and approvals are required?

Required permission scopes: ontologies:write. OAuth uses current workspace membership; API keys use their assigned scopes and grants. Discovery can exclude tools the caller cannot use.

Read-only annotation: No. Destructive annotation: No. Follow the operation’s declared contract and any applicable server-side approval policy.

How should I handle retries?

The server marks this operation as idempotent. When an idempotencyKey is accepted, keep the same key only for a retry of the exact same input; use a new key for new work. For 429 responses, honor Retry-After rather than retrying immediately.

Why is this tool missing or returning an error?

Confirm the workspace, resource IDs, and permission scopes. Read the returned error before changing the request. See connection, authentication and troubleshooting for sign-in, scope, resource access, and rate-limit errors.