Skip to main content
Glama

get_documents

Read-onlyIdempotent

Lista los documentos del workspace (SIN contenido — solo metadata: id, name, date, updated_at, parent_document_id, order).

Usar para: navegar la estructura de documentos, listar documentos disponibles, encontrar IDs.
Para encontrar un documento POR NOMBRE: `name` acá, o find_documents si no sabés en qué workspace está.
Para leer el contenido de un documento específico: usar get_document(document_id).
Para buscar por contenido: usar search_documents(query).

Sin parent_document_id: lista todos. Con parent_document_id=null: solo raíz. Con ID específico: hijos de ese documento.

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

Input Schema

NameRequiredDescriptionDefault
nameNoFiltrar por nombre (contiene, sin distinguir mayúsculas)
limitNoMáximo resultados (default: 50)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo
parent_document_idNoFiltrar por documento padre. Omitir = todos los documentos. null = solo raíz. ID = hijos de ese documento

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally; the description's added value is the explicit warning that no document content is returned, only metadata, which prevents a common misuse. It stops short of stating result ordering or how limit interacts with large workspaces, which would have been the last increment.

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 with the core action and its key constraint, then separated into scannable blocks for usage, routing alternatives, and parameter edge cases. No filler sentences; each block carries distinct information an agent needs.

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?

No output schema exists, and the description compensates by naming the metadata fields returned and explicitly excluding content. Combined with full parameter documentation and sibling routing, an agent has everything needed to call this correctly and interpret the result.

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 goes beyond the schema on the genuinely subtle parameter by spelling out the three-way `parent_document_id` behavior (omit = all, null = root only, ID = children). That is exactly the disambiguation the JSON Schema type union leaves ambiguous in practice.

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?

Specific verb + resource + scope: 'Lista los documentos del workspace', immediately bounded with 'SIN contenido — solo metadata' and an explicit enumeration of the returned fields (id, name, date, updated_at, parent_document_id, order). This distinguishes it from content-reading siblings without requiring the schema to be opened.

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?

Provides a 'Usar para' block covering navigation, listing, and ID discovery, then explicitly routes each adjacent need: name lookup → `name` here or find_documents, content → get_document(document_id), content search → search_documents(query). When-to-use and when-to-use-something-else are both stated.

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