Skip to main content
Glama

find_documents

Read-onlyIdempotent

Busca documentos POR NOMBRE en TODOS los workspaces del usuario, en una llamada. Devuelve id, name, workspace (id y nombre), parent_document_id y updated_at.

Usar cuando el usuario nombra un documento ("actualizá el Business Overview") y no se sabe en qué workspace está.
Si vuelve más de uno con nombre parecido, preguntá cuál antes de escribir.

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

Input Schema

NameRequiredDescriptionDefault
nameYesParte del nombre del documento
limitNoMáximo (default: 30)

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restatement. The description adds real behavioral value beyond that: the cross-workspace reach in a single call, the returned field set, and the ambiguity-handling rule. It does not mention result ordering or what happens on zero matches, which keeps it short of a 5.

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?

Three tight sentences with the core capability front-loaded, followed by the usage trigger and the ambiguity rule. No filler and nothing buried.

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?

There is no output schema, so the description correctly spends a sentence enumerating return fields, and it defines scope, trigger and edge-case handling. For a two-parameter read tool this is everything an agent needs to select and call it correctly.

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?

Schema coverage is 100%, and the schema already explains that name is a partial name fragment and that limit defaults to 30. The description's 'POR NOMBRE' phrasing mirrors rather than extends that, so the baseline of 3 applies.

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 with explicit scope: search documents BY NAME across ALL of the user's workspaces in one call. It also enumerates the returned fields (id, name, workspace id/name, parent_document_id, updated_at), so the agent knows exactly what it gets back and how this differs from a generic document fetcher.

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 an explicit trigger condition — the user names a document and it is unknown which workspace holds it — plus follow-up guidance: if several similar names come back, ask which one before writing. That covers both when to use it and what to do with ambiguous results.

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