Skip to main content
Glama

get_entity_wiki

Read-onlyIdempotent

El artículo del WIKI del Atlas de una entidad (persona, proyecto, organización, etiqueta): qué es, historia, estado actual y gente involucrada, escrito desde TODO el material del workspace donde aparece y regenerado cuando llega material nuevo.

Es la mejor fuente para "¿qué es X?", "¿en qué está X?", "¿quién está en X?".
Trae además:
  citas            a qué recap/documento/nota se refiere cada [n] del artículo, con la tool para abrirlo
  enlaces          las entidades que el artículo menciona
  mencionada_en    las páginas de otras entidades que hablan de ésta
  ultimas_apariciones  lo más nuevo donde aparece (puede ser posterior al artículo)
  tareas_abiertas  con estado real

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_wiki"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYesID de la entidad (de recall o search_entities)
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.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the article is regenerated when new material arrives, and 'ultimas_apariciones' may be newer than the article itself — an important freshness caveat. It does not cover failure modes (e.g. entity with no wiki yet) or auth/rate limits.

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?

Front-loaded with the core definition and the 'best source for' routing sentence, then a scannable bullet list of returned sections. Slightly verbose in the opening sentence, but every bullet carries distinct information about the payload.

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

Completeness4/5

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

With no output schema, the description correctly compensates by enumerating the returned fields (citas, enlaces, mencionada_en, ultimas_apariciones, tareas_abiertas) and their meaning. Only the empty/no-article case and the shape of 'citas' entries are left unspecified.

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%, so both entity_id and workspace_id are already documented, including the 'omit if token has fixed workspace' rule. The description adds no parameter-level 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.

Purpose5/5

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

States a specific verb and resource ('el artículo del WIKI del Atlas de una entidad') and enumerates the content dimensions (qué es, historia, estado actual, gente involucrada) plus its provenance ('escrito desde TODO el material del workspace'). An agent can distinguish this read of a synthesized article from entity-detail or document-listing siblings without opening the schema.

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

Usage Guidelines4/5

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

Gives explicit when-to-use triggers via the quoted question patterns ('¿qué es X?', '¿en qué está X?', '¿quién está en X?') and calls itself 'la mejor fuente' for them. It stops short of naming when NOT to use it or pointing to a concrete alternative such as get_entity_details or refine_entity_wiki.

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