Skip to main content
Glama

Tax record books (self-employed)

list_tax_documents
Read-onlyIdempotent

Entries of the self-employed tax record books of a fiscal year (Spain: income, expenses, investment goods and provisions books), one per tax document (invoice), as shown in Cuéntamo: accrual and invoice dates, invoice number, fiscal amount with VAT, VAT rate(s), income-tax withholding, tax-return box, depreciation, payment status and completeness. Filters by book, accrual date range, client or supplier, tax-return box and missing data; paginated. Client and supplier names and tax ids come partially hidden unless reveal_third_parties is true; they are returned under untrusted with the concept and notes. Read-only. Needs the self-employed module.

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_tax_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookNoAccount book id (from list_books). Optional if the user has only one.
yearNoFiscal year. Default: current year.
limitNoDefault: 50.
offsetNoFor the next page. Default: 0.
date_toNoAccrual date to (inclusive).
tax_boxNoTax-return box code (e.g. 0186), or "unclassified".
tax_bookNoDefault: all.
date_fromNoAccrual date from (inclusive), e.g. the first day of a quarter.
third_partyNoPart of the client or supplier name or tax id (accents and case ignored). Matches on the full data even when the answer hides it.
incomplete_onlyNoOnly entries missing the client/supplier or the invoice number.
reveal_third_partiesNoFull names and tax ids of clients, suppliers and payees. Default false: they come partially hidden (first letters of each word, first and last characters of the tax id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful behavior beyond that: results are paginated, client/supplier names and tax ids are partially hidden unless reveal_third_parties is true, hidden third-party data is returned under an untrusted section, and the self-employed module is required.

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 dense and front-loads the core resource definition before filters and privacy caveats. It is appropriately sized for an 11-parameter tool, though the single long paragraph could be more scannable and 'Read-only' lightly repeats the annotation.

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?

With no output schema and 11 optional parameters, the description does substantial work by listing returned fields and explaining the untrusted third-party return behavior. It is nearly complete, though it does not describe response ordering, pagination metadata, or the exact response envelope.

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 description coverage is 100%, so every parameter is already documented in the input schema. The description reinforces the filtering concepts and the privacy behavior of reveal_third_parties, but it does not add syntax, defaults, or semantics beyond what the schema already provides.

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 states a specific resource and scope: entries from the self-employed tax record books for a fiscal year, one per tax document/invoice, across Spain-specific books. It distinguishes the tool from a single-document lookup such as get_tax_document by describing list-style filtering and pagination.

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

Usage Guidelines3/5

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

The description gives useful context for use: it can filter by book, accrual date range, client/supplier, tax-return box, and missing data, and it notes that the self-employed module is required. However, it does not explicitly say when to use this tool instead of siblings like get_tax_document, list_books, or search_transactions, so the routing guidance is only implied.

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