Skip to main content
Glama
Sign In

secondbrain

by media.secondbrain
OverviewDiscussionsAdmin

get_documents

Read-only

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.

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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds meaningful value beyond that by stating no content is returned and enumerating the exact metadata fields (id, name, date, updated_at, parent_document_id, order), which shapes how an agent plans follow-up calls.

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?

Front-loaded with purpose and scope, then a clean routing block, then parameter semantics. Every sentence carries routing or semantic value, though the parent_document_id explanation overlaps with the schema already.

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, yet the description compensates by listing the returned metadata fields, and the routing covers all obvious alternatives. An agent has everything needed to call it 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 adds the subtle tri-state semantics of parent_document_id (omit = all, null = root only, specific ID = children) in a form slightly distinct from the schema wording. It reinforces rather than merely repeats 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?

States a specific verb and resource ('Lista los documentos del workspace'), and immediately scopes it ('SIN contenido — solo metadata') with an explicit field list. It is clearly distinguishable from get_document, search_documents, and find_documents, which it names directly.

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?

Gives explicit when-to-use scenarios (navigate structure, list documents, find IDs) and routes each adjacent case to the right sibling: get_document for content, search_documents for content search, find_documents for name lookup in unknown workspaces. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All secondbrain toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources