Skip to main content
Glama

refine_entity_wiki

DestructiveIdempotent

Guarda en el WIKI del Atlas una conclusión sobre una entidad: algo SÓLIDO que el wiki no dice o dice mal (el rol o cargo de una persona, qué es un proyecto, con quién trabaja, un estado que sale de juntar varias fuentes).

El wiki lo escribe de noche un modelo chico con ~20 fragmentos; una conversación puede
cruzar muchas más fuentes. Lo guardado queda como aporte permanente: el wiki se
reescribe en el momento usándolo como fuente prioritaria, y cada reescritura futura lo
vuelve a leer. Es una escritura: para cuando la persona pide dejarlo asentado, o lo
acepta cuando se le ofrece.

tipo:
  definicion   qué es / qué rol tiene. "Pablo Ronco es el CTO de Veritran; …"
  conclusion   algo que sale de cruzar fuentes: estado, relación, patrón
  correccion   el wiki dice algo mal; decí qué es lo correcto

Qué SÍ: hechos que las fuentes sostienen, escritos para durar.
Qué NO: opiniones tuyas, recomendaciones, el pedido del usuario, cosas de "esta semana"
que envejecen en días, o lo que el wiki ya dice. Mirá get_entity_wiki (trae "aportes")
antes; si un aporte tuyo quedó viejo, reemplazalo con `reemplaza`.
Un aporte por entidad y por idea; texto autocontenido (nombrá a la entidad).

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>",
      "tipo": "<tipo>",
      "texto": "<texto>"
    },
    "name": "refine_entity_wiki"
  }
}

Input Schema

NameRequiredDescriptionDefault
tipoYes
textoYesLa conclusión, en español, autocontenida. 1–5 oraciones.
basado_enNoLas fuentes del workspace en que se apoya
entity_idYesID de la entidad (de recall o search_entities)
reemplazaNoID de un aporte anterior que éste reemplaza
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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true; the description adds real context beyond them: the entry becomes permanent, the wiki is rewritten immediately using it as a priority source, and every future rewrite re-reads it. It also explains how the wiki is normally produced (nightly, small model, ~20 fragments) so the agent knows why a conversation may add value. It stops short of saying how an aporte can be removed or that replacements are irreversible, which is the residual gap under destructiveHint=true.

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 purpose, then trigger, then the tipo taxonomy, then the SÍ/NO filter and the get_entity_wiki prerequisite. The paragraph on the nightly small-model process slightly exceeds the minimum needed, but it justifies what qualifies as a valuable entry rather than padding.

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?

For a 6-parameter write with no output schema, the description covers what qualifies, what to exclude, when to act, how to supersede prior entries, and the persistence lifecycle. Workspace scoping is handled by the schema, so nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is already 83%, so the baseline is 3; the description goes further by defining the three `tipo` values with examples (definicion/conclusion/correccion) and explaining `reemplaza` as the mechanism for superseding a stale aporte. It also adds a content rule for `texto` (autocontenido, nombra la entidad) beyond the schema's length bounds. `basado_en` is left entirely to the schema, which is reasonable given it is documented there.

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+resource in the first line: saving a conclusion about an entity into the Atlas WIKI, and qualifies what counts as solid (role, what a project is, who someone works with). It is clearly distinct from the read-side sibling it names, get_entity_wiki.

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?

Explicit when-to-use ('para cuando la persona pide dejarlo asentado, o lo acepta cuando se le ofrece'), explicit when-not ('Qué NO: opiniones tuyas, recomendaciones, el pedido del usuario, cosas de esta semana'), and a named prerequisite alternative: check get_entity_wiki (trae 'aportes') first and use `reemplaza` if a prior aporte went stale.

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