Skip to main content
Glama

dissociate_document_entity

DestructiveIdempotent

Desvincula una entidad del knowledge graph de 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": "dissociate_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 flag destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is known. The description adds nothing beyond the name: it does not say whether relations attached to that entity/document pair are also removed, whether the entity survives elsewhere, or whether the operation is reversible — all critical for a destructive call.

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 front-loaded sentence with zero padding — the verb and both resources appear immediately. It is efficient, though the terseness is part of why behavioral detail is missing.

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 destructive, non-read-only mutation with no output schema, the definition says nothing about effects, side effects on existing relations, or error conditions. The 100% schema coverage covers inputs, but the destructive semantics an agent needs before calling are absent.

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% and all three parameters (document_id, entity_id, workspace_id) are documented in the schema, including the workspace_id fallback behavior. The description adds no extra meaning beyond the schema, so the baseline 3 applies.

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?

"Desvincula una entidad del knowledge graph de un documento" gives a specific verb (unlink) and both resources (entity, document), so the operation is unambiguous and reads as the inverse of the sibling associate_document_entity. It stops short of naming that sibling explicitly, so differentiation relies on the agent noticing the antonym.

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?

The description contains no when-to-use or when-not-to-use guidance, no mention of re-linking via associate_document_entity, and no note that this removes the link rather than the entity itself. The agent must infer all routing from the tool name alone.

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