Skip to main content
Glama
OpenLMNP

OpenLMNP

Generate Tax Return

generate_tax_return
Idempotent

Generates the French LMNP tax return PDF (forms 2031-SD and 2033-A to 2033-D) for a given fiscal year, recalculating figures when needed and returning key declaration amounts.

Instructions

Génère la liasse fiscale LMNP au format PDF (formulaires 2031-SD, 2033-A, 2033-B, 2033-C et 2033-D) pour un exercice fiscal donné. L'exercice est recalculé avant la génération si nécessaire. Retourne un résumé des montants clés de la déclaration ; le PDF lui-même n'est pas conservé sur le serveur, il se télécharge depuis la page Exercices fiscaux.

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": {
      "year": "<year>"
    },
    "name": "generate_tax_return"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesAnnée fiscale pour laquelle générer la liasse (ex : 2025)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / year / description
      Added value: +"Année fiscale pour laquelle générer la liasse (ex : 2025)"
  2. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare idempotent and non-destructive behavior. The description adds material context beyond that: the fiscal year may be recalculated before generation if necessary, it returns a summary of key declaration amounts, and the PDF is not stored on the server but downloaded from the 'Exercices fiscaux' page. Permissions and error behavior are not covered, but the key side effects and output handling are disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three front-loaded sentences, each carrying a distinct fact: scope and forms, recalculation behavior, and return/non-storage behavior. There is no filler or repetition.

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 one-parameter generation tool with no output schema, the description covers the main unknowns: what is generated, that recalculation may occur, that a summary is returned, and that the PDF is not persisted server-side. It does not detail the summary fields or prerequisites, but those gaps are minor given the tool's low complexity.

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?

The single required 'year' parameter has 100% schema description coverage, so the schema already explains it. The description only restates it as 'exercice fiscal donné' and mentions recalculation, adding no format or semantic detail beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('Génère'), resource ('liasse fiscale LMNP'), output format ('PDF'), exact forms (2031-SD, 2033-A to 2033-D), and scope ('pour un exercice fiscal donné'). An agent can distinguish this from siblings like compute_fiscal_year or generate_fec without opening the schema.

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?

It gives clear context that the tool generates an LMNP tax return PDF for a fiscal year, but it does not explicitly say when to use this versus compute_fiscal_year, get_fiscal_year, or other related tools, nor does it state exclusions. Usage is implied by the purpose rather than routed.

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