list_documentsList the 100 most recent documents for this account with id, filename, status (pending/done/failed), doc_type and primary reference number.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description goes beyond the readOnlyHint annotation by specifying the 100-document limit, account scoping, and the exact set of fields returned (including status enum values). This provides clear behavioral expectations, though it doesn't cover edge cases like empty accounts or pagination details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that conveys the action, scope, and result fields with no redundant information. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless list tool, the description fully covers what the tool does and what it returns, including the 100-document limit and field names. There is no output schema, so this textual description carries the full burden and meets it well.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters, so the baseline is 4. The description adds no parameter details because none exist, and this is acceptable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states 'List the 100 most recent documents for this account' with a specific verb and resource, and lists the returned fields (id, filename, status, doc_type, primary reference number). This clearly distinguishes it from sibling tools like get_document (single document) or export_documents (exporting).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies its use for browsing recent documents but does not explicitly compare with alternatives like get_document or export_documents. There is no when-not-to-use guidance or mention of sibling tools, so it's adequate but not fully explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action and resource: single extraction, batch extraction, document retrieval, listing, export, corrections, reconciliation, and account usage. extract_bol vs extract_batch is the only close pair, but single vs batch is a clear distinction.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: export_documents, extract_batch, extract_bol, get_document, get_related_documents, get_usage, list_documents, save_corrections. No mixed styles or vague verbs.
8 tools is well within the ideal 3-15 range. Each tool earns its place by covering a distinct step in the document processing workflow, with no redundancy or bloat.
The toolkit covers the full lifecycle: extraction (single and batch), retrieval (get/list), update (save_corrections), export, reconciliation, and account management. There are no obvious gaps that would hinder agent workflows.