Skip to main content
Glama

get_entity_details

Read-onlyIdempotent

Obtiene el detalle completo de una entidad del knowledge graph por ID.

Retorna: id, canonical_name, type, description, context (texto libre de contexto), aliases (nombres alternativos), relations_cache (relaciones resumidas), occurrence_count (veces mencionada), created_at, updated_at.

Además dos señales calculadas sobre el CONTENIDO asociado, no sobre el nombre:
  similar_by_content   → entidades que hablan de lo mismo. "likely_duplicate: true" marca las
                         que además tienen el nombre parecido: casi siempre es la misma cosa
                         cargada dos veces, y conviene proponer merge_entities.
  suggested_relations  → relaciones que NO están cargadas pero el contenido sugiere, con
                         cuántas veces aparecen juntas y cuántas veces por encima del azar.
                         Para crearlas: add_entity_relation.

wiki_summary es el resumen del artículo del wiki (fresco); para el artículo entero, get_entity_wiki.
occurrence_count = en cuántas fuentes (recaps, docs, notas, tareas) aparece.

Usar cuando necesitas todos los datos de una entidad, incluyendo contexto y aliases, después de encontrar su ID con search_entities.

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_id": "<entity_id>"
    },
    "name": "get_entity_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYesID de la entidad
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

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description instead adds genuinely new behavior: the two computed signals are derived from content rather than name, likely_duplicate means 'casi siempre es la misma cosa cargada dos veces', suggested_relations are not yet persisted and carry co-occurrence counts, and occurrence_count is defined as number of distinct sources. It stops short of noting limits or what happens with an unknown ID.

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

Conciseness5/5

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

Front-loads the purpose in one line, then a compact return-field list, then the two computed signals as indented sub-bullets, then the disambiguation and usage rule. Every sentence carries distinct information; nothing repeats the title or schema.

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

Completeness5/5

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

There is no output schema, so the description must carry the return contract, and it does: it enumerates all nine fields, explains the two derived signals, defines occurrence_count precisely, and routes to get_entity_wiki for the full text. Combined with the annotations, an agent has everything needed to call and interpret the result.

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 coverage is 100%, so both entity_id and workspace_id are already documented in the schema, including the fallback of passing a workspace name. The description adds only the implicit 'ID from search_entities' workflow and says nothing further about workspace_id, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Obtiene el detalle completo de una entidad del knowledge graph por ID') and immediately delimits scope against get_entity_wiki ('para el artículo entero, get_entity_wiki'), so an agent can separate it from its nearest sibling without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Usar cuando necesitas todos los datos de una entidad... después de encontrar su ID con search_entities') and names the downstream alternatives for each returned signal: merge_entities for likely_duplicate=true, add_entity_relation for suggested_relations, get_entity_wiki for the full article. This is when-to-use plus routing, not just context.

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