Skip to main content
Glama

get_definitions

Read-onlyIdempotent

Obtiene las definiciones del workspace, con filtro opcional por entidad

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

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo (default: 50)
offsetNoPara paginación
entity_idNoFiltrar por entidad relacionada
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

C2.9/5.0
Behavior3/5

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

Annotations are rich (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the safety profile is already fully conveyed. The description adds only the workspace scoping and optional entity filter, with nothing about result volume, ordering, or what a caller receives — a lower bar applies, but it contributes little.

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?

A single compact clause, front-loaded with the verb and resource, with no filler. Brevity is achieved, but the space saved is spent nowhere useful — the sentence is short because it omits rather than because it is economical.

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

Completeness3/5

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

For a read-only, fully-annotated, 4-optional-parameter list tool with no output schema, the definition covers the minimum: what is fetched and that filtering is optional. However, the concept of 'definiciones' and the shape of the returned data are left entirely unexplained, which is the main thing a caller needs here.

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 100% schema description coverage the schema already documents limit, offset, entity_id, and workspace_id in detail (including that omitting workspace_id returns all workspaces). The description's only mention of entity filtering duplicates the schema, adding no new semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

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

States a verb ('Obtiene') and a resource ('definiciones del workspace') plus an optional entity filter, but 'definiciones' is never defined — an agent cannot tell what a definition actually is or how it differs from sibling knowledge/entity tools like get_knowledge or get_entity_details. Adequate but leaves the core object ambiguous.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no exclusions, and no mention of alternatives among the many read siblings. The only conditional hint is 'con filtro opcional por entidad', which restates a parameter rather than describing a usage scenario.

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