Skip to main content
Glama

Tax document (invoice) details

get_tax_document
Read-onlyIdempotent

One tax document (invoice) of the self-employed tax books, by id (from list_tax_documents): dates (invoice, operation, registration, accrual), fiscal amount, tax base and VAT (per rate when the invoice has several), VAT exemption, income-tax withholding, intra-community or reverse-charge treatment, deductible share for income tax and VAT (the document's own value or the one inherited from its category or tag), depreciation, tax-return box, and the payments linked to it. The client or supplier comes partially hidden unless reveal_third_parties is true; it is returned under untrusted with the notes and line descriptions. Read-only. Needs the self-employed module.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_tax_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTax document id.
bookNoAccount book id (from list_books). Optional if the user has only one.
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

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the privacy behavior (third parties partially hidden unless reveal_third_parties is true), where that untrusted content is returned ('under `untrusted` with the notes and line descriptions'), and the module requirement. This is exactly the kind of behavioral context the schema and readOnlyHint annotations do not convey.

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?

Front-loaded with the identity of the resource and the id source, followed by a dense but purposeful enumeration of returned fields. The field list is long but earns its place because there is no output schema, though a shorter lead sentence would improve scanability.

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?

Since no output schema exists, enumerating the returned data (dates, amounts, VAT breakdown, withholding, deductibility, payments) is valuable and makes the tool callable with confidence. Minor gaps remain: no mention of what happens for an invalid or inaccessible id, and no note on whether linked payments are limited in number.

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 coverage is 100%, so all three parameters are already documented in the schema, and the reveal_third_parties description largely restates the schema's own masking explanation. The description does not touch the `book` parameter at all, so it adds little meaning beyond the structured fields; baseline 3 applies.

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?

States a specific verb and resource with scope: 'One tax document (invoice) of the self-employed tax books, by id (from list_tax_documents)'. It is immediately distinguishable from list_tax_documents and from the aggregate summary tools in the sibling set.

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?

Provides clear usage context by naming the source of the id (list_tax_documents) and the module prerequisite ('Needs the self-employed module'). It does not explicitly say when to prefer this over get_income_tax_summary or get_tax_periods, but the single-document scope makes the boundary reasonably inferable.

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