Skip to main content
Glama

add_entity_identifier

Idempotent

Upsert a per-source identifier for an entity so records from different sources can be matched to the same entity identity.

Instructions

Upsert a per-source entity identifier.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity_type": "<entity_type>",
      "entity_id": "<entity_id>",
      "source": "<source>",
      "identifier": "<identifier>"
    },
    "name": "add_entity_identifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
entity_idYes
identifierYes
entity_typeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description's 'Upsert' is consistent with idempotentHint and adds a small amount of conflict-behavior context, but it says nothing about what a source-scoped identifier is attached to, what happens to an existing row on match, or any permission requirements for a write operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the verb and key qualifier front-loaded; nothing is padded. Its brevity is appropriate structurally, though the terseness borders on under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. But for a non-read-only tool with four required, fully undocumented parameters, the description does not supply enough for an agent to call it correctly the first time.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four required parameters, so the schema carries no meaning at all. The description only vaguely gestures at 'per-source' without defining what a source is, and says nothing about entity_type values, identifier formats, or how entity_id relates to an existing entity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Upsert') and resource ('per-source entity identifier'), which is more informative than the tool name's 'add_'. However, it gives no hint of how an identifier differs from the entity itself, and nothing distinguishes it from siblings like add_entity or seed_entity_identifiers, leaving the resource concept underspecified.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus add_entity, update_entity, or seed_entity_identifiers, and no mention of prerequisites or conflict scenarios. The word 'Upsert' weakly implies 'use this when the identifier may already exist,' but that inference is left entirely to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.