Skip to main content
Glama

My document folders

documents_folders
Read-onlyIdempotent

The eight fixed document folders with the real number of your documents in each (0 is a real zero) and the latest issue date. partial_sources lists sources that failed to load.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world). The description adds useful semantics beyond them: counts are exact including real zeros, and partial_sources signals degraded results when a source fails. It doesn't explain ordering of the folders or what 'latest issue date' means when a folder is empty.

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 sentence carries the scope and result semantics with no filler. Slight weakness: the partial_sources note trails after the main clause and assumes the reader knows the response shape, but nothing is wasted.

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 zero-parameter read tool with full annotation coverage, the description covers what is returned well enough. However, with no output schema, it could do more: it never enumerates the eight folders or explains the date format, which an agent may need to interpret results.

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?

Zero parameters, so the baseline is 4. The description also clarifies the shape of the result fields (counts including genuine zeros, latest issue date, partial_sources), which adds meaning even though there is no schema to compensate for.

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?

States a specific resource and scope: the eight fixed document folders, each with document counts and latest issue date. It also explains what partial_sources means. It doesn't distinguish itself from siblings like my_order_documents or documents_list, but the 'fixed folders' framing is reasonably self-identifying.

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?

No when-to-use guidance is given. The description never says to prefer this over documents_list when an overview by folder is wanted, nor does it mention prerequisites or that it takes no parameters by design.

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