Skip to main content
Glama
OpenLMNP

OpenLMNP

Get Fiscal Year

get_fiscal_year
Read-only

Retrieves complete fiscal-year details for a specified year, including fiscal result, income, expenses, depreciation, opening balances, VAT, and 2031/2033 form data for LMNP tax reporting.

Instructions

Retourne le détail complet d'un exercice fiscal par son année : résultat fiscal, recettes, charges, amortissements (total, plafonné, reporté), soldes d'ouverture d'une reprise de dossier (amortissements différés, déficits par millésime, cumul d'amortissements de contrôle, provenance), TVA, form_data du formulaire 2031/2033, et informations de télétransmission.

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": "get_fiscal_year"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesAnnée fiscale à récupérer, ex: 2024

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 à récupérer, ex: 2024"
  2. First observedv0.1.1

TDQS

A3.5/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes the safe-read profile, and the description adds substantial behavioral value by itemizing the returned payload, including reprise-de-dossier fields (amortissements différés, déficits par millésime, cumul de contrôle, provenance) that an agent could not otherwise anticipate. It does not state what happens when the year has no fiscal record, which is the main remaining behavioral gap.

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?

One front-loaded sentence that opens with the operation and then lists returned fields, with zero filler or restatement of the title. The field enumeration is long but every clause names real data returned, so it earns its length rather than padding.

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 one required parameter, no output schema, and only readOnlyHint as annotation, the description does the heavy lifting by describing the return payload in place of a missing output schema. The only shortfall is absent error/empty-result behavior for a year with no fiscal record.

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% and the single parameter 'year' is well documented with an example (2024), so the schema already carries the semantics. The description only reinforces that the year identifies the fiscal exercise being fetched; it adds no format, range, or lookup-failure detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Retourne le détail complet d'un exercice fiscal par son année') and enumerates exactly what data the detail includes (résultat fiscal, recettes, charges, amortissements, TVA, form_data 2031/2033, télétransmission). An agent can distinguish this from write or compute tools, but the description never contrasts it with the sibling 'list_fiscal_years' or 'compute_fiscal_year', so the single-year read distinction must be inferred.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative, despite siblings like 'compute_fiscal_year', 'list_fiscal_years', and 'get_projection' that could plausibly be confused. The only implicit cue is 'par son année', which suggests a single-year lookup rather than a list.

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