Skip to main content
Glama

associate_document_entity

Idempotent

Vincula una entidad del knowledge graph a un documento

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": {
      "document_id": "<document_id>",
      "entity_id": "<entity_id>"
    },
    "name": "associate_document_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYesID de la entidad
document_idYesID del documento
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, closed-world mutation, so the safety profile is covered. The description adds nothing beyond that: it does not say what happens if the link already exists (relevant given idempotentHint), whether permissions or workspace scoping are required, or what error conditions look like.

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, well-formed sentence with no wasted words, front-loading the action and resource. It is efficient, though its brevity contributes to the gaps in usage and behavioral guidance.

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?

For a mutation tool with no output schema, the description should clarify idempotent behavior, preconditions, and whether an existing link is overwritten or rejected. With annotations covering only the safety profile, the description leaves the agent without enough context to call it confidently in edge cases.

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

Parameters3/5

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

Schema description coverage is 100%, with all three parameters (document_id, entity_id, workspace_id) documented in the schema itself, so the baseline is 3. The description adds no additional meaning about parameter formats, ID types, or the workspace fallback behavior.

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

Purpose4/5

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

The description states a specific verb ('Vincula') and resource ('una entidad del knowledge graph a un documento'), so the agent knows this creates a link between an entity and a document. It does not, however, distinguish itself from the sibling dissociate_document_entity, which is the obvious inverse operation an agent would need to disambiguate.

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 guidance on when to use this tool versus alternatives, no mention of prerequisites (e.g., the entity and document must already exist), and no reference to dissociate_document_entity as the inverse. The agent must infer the usage context entirely.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources