Skip to main content
Glama

get_knowledge

Read-onlyIdempotent

Lista todas las entidades del knowledge graph del workspace. El knowledge graph almacena personas, proyectos, organizaciones y conceptos que aparecen en notas, documentos y reuniones.

Tipos de entidades:
- person: personas (clientes, colegas, contactos)
- project: proyectos activos o históricos
- organization: empresas, clientes, organizaciones
- category: categorías o temas generales
- entity: entidades genéricas

Las ETIQUETAS también son entidades de esta tabla, no una cosa aparte: lo
que las separa es el tipo. Y las condiciones de un tablero se escriben con
los IDS de estas entidades, así que de acá salen.

Ordenado por occurrence_count DESC (más mencionadas primero). Para buscar una entidad específica, usar search_entities(query) en vez de cargar todas.
Retorna: id, type, canonical_name, aliases, description, context, occurrence_count, relations_cache.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFiltrar por tipo de entidad
limitNoMáximo resultados (default: 200)
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, and closed-world behavior, so the safety profile is covered. The description adds real context beyond that: default ordering by occurrence_count DESC, the full list of returned fields, and the non-obvious fact that labels are stored as entities and that board conditions reference these IDs. It stops short of describing pagination or how limit interacts with the default 200.

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?

The purpose is front-loaded in sentence one, and the bulleted type taxonomy is scannable rather than dense prose. A few phrases, such as the aside about ETIQUETAS and board-condition IDs, are conversational, but they carry genuine domain information rather than filler.

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 compensates by enumerating the returned fields and the sort order, and it covers filtering, scope, and the sibling alternative. The only real gap is that the default cap of 200 results and what happens when the graph exceeds it is never discussed.

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 100%, so the baseline is 3, but the description earns more by explaining what each enum value of `type` actually denotes (person, project, organization, category, entity), which the schema lists only as bare strings. It also clarifies the workspace_id omission case, though limit behavior is left entirely to the schema.

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?

The first sentence states a specific verb and resource ("Lista todas las entidades del knowledge graph del workspace") and the description goes on to define exactly what a knowledge graph entity is here. It explicitly differentiates itself from search_entities, so an agent can choose between them without inspecting schemas.

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?

It gives an explicit alternative and the condition that selects it: "Para buscar una entidad específica, usar search_entities(query) en vez de cargar todas." It also signals the workspace_id can be omitted when the token is workspace-scoped, which is usage guidance, not just schema restatement.

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