Skip to main content
Glama

search_entities

Read-onlyIdempotent

Busca entidades en el knowledge graph por nombre (búsqueda parcial, case-insensitive sobre canonical_name).

Usar cuando:
- El usuario menciona el nombre de una persona, proyecto u organización y necesitas su ID
- Quieres verificar si una entidad ya existe antes de crearla
- Necesitas encontrar una entidad pero no tienes su ID

Busca en el nombre canónico Y en los alias, sin distinguir tildes ni mayúsculas
("tokenizacion" encuentra "Tokenización"). Ordena: coincidencia exacta, después
las que empiezan igual, después por apariciones.

Retorna: id, canonical_name, type, description, occurrence_count (en cuántas fuentes
aparece), aliases, has_wiki (si tiene artículo: leerlo con get_entity_wiki).

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": {
      "query": "<query>"
    },
    "name": "search_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFiltrar por tipo (omitir para buscar en todos)
limitNoMáximo resultados (default: 10)
queryYesTexto a buscar en el nombre canónico de la entidad (parcial, ej: 'Agus' encuentra 'Agustín García')
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 safety is covered. The description adds genuinely new behavioral facts: matching spans canonical_name and aliases, accents and case are ignored ('tokenizacion' finds 'Tokenización'), and results are ranked exact match first, then prefix, then by occurrence count. It also points to get_entity_wiki when has_wiki is true.

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-loaded one-line purpose, then a bulleted when-to-use block, then matching/ranking rules, then the return fields as a labeled list. Every section carries distinct information with no restated schema text.

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?

With no output schema available, the description compensates by enumerating the returned fields (id, canonical_name, type, description, occurrence_count, aliases, has_wiki) and the follow-up tool for wiki content. Combined with the 100%-documented schema and the safety annotations, an agent has everything needed to call and interpret this tool.

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 and the type enum, limit default and workspace_id fallback are already documented. The description still adds value by explaining that the query matches aliases and is accent-insensitive, and by tying the ranking to occurrence_count, which informs how limit should be set.

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?

Opens with a specific verb and resource: searching entities in the knowledge graph by name, and immediately qualifies the match semantics (partial, case-insensitive over canonical_name). An agent can distinguish this from document or workspace search 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?

A dedicated 'Usar cuando' block gives three concrete triggers (need an ID for a mentioned entity, verify existence before creating, find an entity without an ID), which is strong when-to-use guidance. It stops short of naming exclusions or alternatives such as search_documents or search_workspace for non-entity lookups, so routing between search tools still requires inference.

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