Skip to main content
Glama
OpenLMNP

OpenLMNP

Compute Fiscal Year

compute_fiscal_year
Idempotent

Calculates a full LMNP fiscal year result for a given year, including income, expenses, capped/reported depreciation, net taxable result, and VAT balance; creates the year if missing.

Instructions

Calcule le résultat fiscal complet d'un exercice LMNP pour une année donnée : recettes, charges, amortissements (avec plafonnement et report), résultat fiscal net, et solde TVA. Crée l'exercice s'il n'existe pas encore. Tous les montants sont retournés en euros.

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

Input Schema

NameRequiredDescriptionDefault
yearYesAnnée fiscale à calculer (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 à calculer (ex : 2025)"
  2. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare idempotentHint=true and destructiveHint=false, so the description's disclosure that the tool creates the fiscal year when it does not exist is genuinely additive — it reveals a write side effect an agent would not otherwise expect from a "compute" tool. It also states that all amounts are returned in euros and that depreciation involves plafonnement and report, which is real behavioral context. It does not say what happens to a previously computed year on re-run, which would have completed the idempotency picture.

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?

Three sentences, front-loaded with the output inventory, then the creation side effect, then the unit convention — each sentence carries distinct information with no filler. The dense parenthetical about plafonnement and report is slightly compressed but not wasteful.

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, the description correctly takes on the burden of describing return values and does so concretely, plus it flags the create-if-missing side effect and the currency. What remains uncovered is re-computation semantics and failure cases, which matters somewhat for an idempotent tool that mutates state.

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?

There is a single parameter with 100% schema description coverage, so the schema already carries the meaning. The description reinforces it with "pour une année donnée" and the euro-unit convention, but adds no format, range, or boundary rules beyond the schema's example of 2025. 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?

The description opens with a specific verb and resource ("Calcule le résultat fiscal complet d'un exercice LMNP") and enumerates the computed components: recettes, charges, amortissements avec plafonnement et report, résultat fiscal net, solde TVA. That enumeration distinguishes it from read-oriented siblings like get_fiscal_year or narrower compute_* tools, though it never names an alternative explicitly.

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?

Usage is implied rather than stated: an agent can infer it should call this to obtain a full fiscal-year result, and the note that the exercice is created if absent hints at a first-run scenario. There is no explicit when-to-use vs. get_fiscal_year/compute_depreciation/compute_tva guidance and no stated prerequisites.

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