Skip to main content
Glama

get_entity_suggestions

Read-onlyIdempotent

Las entidades que la IA vio nombradas en los recaps y todavía no están en el Atlas: personas, proyectos, organizaciones por confirmar. De cada una: nombre, tipo, en cuántos recaps apareció y cuáles. Se aceptan o descartan con resolve_entity_suggestion. Sin workspace_id mira todos.

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

Input Schema

NameRequiredDescriptionDefault
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

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 readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds real value beyond them: it enumerates the per-item fields returned (name, type, recap count, which recaps) and explains the downstream accept/discard workflow, which annotations cannot convey. It does not mention ordering or result 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?

Four short sentences, front-loaded with what the tool returns and followed by the action pairing and the scope default. The final 'Sin workspace_id' sentence is redundant with the schema, a minor waste in an otherwise tight definition.

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?

No output schema exists, and the description compensates by listing the per-entity return fields, so an agent knows what it will receive. For a single-parameter, read-only listing tool this is close to complete; only result ordering/volume behavior is left unstated.

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?

With one optional parameter at 100% schema coverage, the schema already documents that workspace_id accepts a UUID or a user-spoken name and that omission means all workspaces. The closing phrase 'Sin workspace_id mira todos' merely restates that, adding no new semantics beyond the schema baseline.

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?

Names a specific resource with a precise state qualifier: entities the AI saw named in recaps that are not yet in the Atlas, broken down into people, projects and organizations. It also names the sibling that consumes them (resolve_entity_suggestion), so an agent can distinguish this read tool from the write tool it pairs with 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 Guidelines4/5

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

Gives clear operational context: these are pending items to be accepted or discarded via resolve_entity_suggestion, and omitting workspace_id scans all workspaces. It lacks an explicit when-not-to-use clause (e.g. versus get_entity_details for already-confirmed entities), but the pending-only scope makes the boundary largely self-evident.

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