Skip to main content
Glama

list_documents

List the workspace's client documents (agreements, NDAs, terms) with their acceptance status. Filter by clientId.

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": "list_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the verb 'List' implies a read-only operation, and the description adds that results include acceptance status. However, it does not disclose pagination, ordering, authentication/rate-limit requirements, or the full return shape, leaving meaningful behavioral gaps for a tool with no annotation coverage.

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?

The description is two sentences and front-loads the tool's purpose before the parameter note, with no wasted words. The large whitespace gap is a formatting artifact rather than content bloat, though it slightly hurts readability.

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 simple list tool with one optional parameter, no output schema, and no annotations, the description covers the core purpose, the key return field (acceptance status), and the filter. It remains incomplete regarding pagination, return structure, and whether all workspace documents are returned, so a 3 is appropriate.

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?

There is one optional UUID parameter with 0% schema description coverage. The description adds the semantic role 'Filter by clientId,' which is useful beyond the schema, but it does not mention that the parameter is optional or explain the expected format, so it only partially compensates for the schema gap.

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

Purpose4/5

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

The description uses a specific verb ('List') and clearly names the resource ('client documents') with examples (agreements, NDAs, terms), which distinguishes it from sibling tools like list_clients and list_invoices. It stops short of explicitly differentiating itself from send_document or other document-related operations, so a 4 rather than a 5.

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 only usage guidance is 'Filter by clientId,' which tells the agent how to use the parameter but not when to use this tool versus alternatives. There are no exclusions, prerequisites, or explicit routing to sibling tools.

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