Skip to main content
Glama
nubiia-dev
by nubiia-dev

list_documents

List documents of a specific type from Holded with filters for date range, contact, payment status, and approval status. Supports pagination and field selection to reduce response size.

Instructions

List all documents of a specific type with optional filters for date range, contact, payment status, approval, and sorting. Supports field filtering to reduce response size. NOTE: a document carries three INDEPENDENT and sometimes-conflicting flags — (1) the stored Paid/Pending badge status (set when the document is imported, NOT recomputed), (2) the real outstanding amount paymentsPending (the authoritative math), and (3) approval (filter with approved). A document can be badge-Paid, math-unpaid, and not-approved all at once, so check the flag you actually mean.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (optional)
paidNoFilter by payment status: 0=not paid, 1=paid, 2=partially paid
sortNoSort order by creation date
limitNoMaximum number of items to return (default: 50, max: 500)
billedNoFilter by billed status: 0=not billed, 1=billed
endtmpNoEnding timestamp (Unix timestamp) for filtering documents by date
fieldsNoSelect specific fields to return (e.g., ["id", "contactName", "total"]). Reduces response size by 70-90%. If not provided, returns default fields: id, contact, contactName, date, tax, total, status, paymentsPending
docTypeYesType of document to list
summaryNoReturn only count and pagination metadata without items (default: false)
approvedNoFilter by approval state: 0=not approved, 1=approved. Maps to Holded `filter=approved-<n>`. Independent of the Paid/Pending badge and of paymentsPending.
starttmpNoStarting timestamp (Unix timestamp) for filtering documents by date
contactidNoFilter documents by contact ID
Behavior5/5

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

The description excels by including a detailed NOTE about the three independent payment status flags (badge, paymentsPending, approval), clarifying potentially confusing behavior. This goes beyond what annotations (none provided) would require.

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 mostly concise with a clear first paragraph and a second paragraph containing essential caveats. The note is somewhat lengthy but justified by the complexity of the payment flags.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 12 parameters and no output schema, the description covers key filtering capabilities and the important flag nuance. It could mention pagination defaults or the summary parameter, but the schema already handles those.

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?

While the input schema covers 100% of parameters with descriptions, the description adds critical context for the 'paid' parameter, explaining it filters on the badge status, not the real outstanding amount. This adds value beyond 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?

The description clearly states the tool lists documents by type with optional filters, using specific verbs and resources. It distinguishes from sibling tools like get_document, create_document, etc., by focusing on listing multiple documents with filtering.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on when to use the tool (listing documents with filters) and includes practical tips like field filtering to reduce response size. However, it does not explicitly mention when not to use it or suggest alternatives like get_document for single documents.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nubiia-dev/mcp-holded'

If you have feedback or need assistance with the MCP directory API, please join our Discord server