Skip to main content
Glama
OpenLMNP

OpenLMNP

Get Projection

get_projection
Read-only

Project multi-year LMNP tax results by estimating income, expenses, depreciation, carryforwards, and micro-BIC comparison across chosen years.

Instructions

Calcule une projection pluriannuelle du résultat fiscal LMNP sur plusieurs années. Pour chaque année : revenus estimés, charges, amortissements (bâti + travaux + mobilier), plafonnement, report cumulé, résultat fiscal net, comparaison micro-BIC. Tous les montants sont en euros.

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

Input Schema

NameRequiredDescriptionDefault
yearsNoNombre d'années à projeter, entre 1 et 15 (défaut : 5)
start_yearNoAnnée de départ de la projection (défaut : année courante)
income_growthNoTaux de croissance annuel des revenus en % (ex : 2 pour +2%/an)
expense_growthNoTaux de croissance annuel des charges en % (ex : 3 pour +3%/an)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.1
    • addedInput schema / properties / expense_growth / description
      Added value: +"Taux de croissance annuel des charges en % (ex : 3 pour +3%/an)"
    • addedInput schema / properties / income_growth / description
      Added value: +"Taux de croissance annuel des revenus en % (ex : 2 pour +2%/an)"
    • addedInput schema / properties / start_year / description
      Added value: +"Année de départ de la projection (défaut : année courante)"
    • addedInput schema / properties / years / description
      Added value: +"Nombre d'années à projeter, entre 1 et 15 (défaut : 5)"
  2. First observedv0.1.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real value beyond that: it discloses the per-year breakdown produced (revenus, charges, amortissements with three components, plafonnement, report cumulé, résultat fiscal net, micro-BIC comparison) and states that all amounts are in euros. What it does not disclose is whether the projection is derived from existing income/expense records or purely from the growth parameters.

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 core purpose in the first sentence, followed by a compact enumeration of per-year outputs and a single currency note. Dense but every element carries information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a domain-specific tax projection with four optional parameters and no output schema, the description does the right thing by enumerating return fields and currency. However, it omits a material behavioural detail: whether the projection uses data already stored in the account (properties, incomes, expenses) or is generated purely from the supplied parameters. That ambiguity matters for correct invocation.

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 years (1-15, default 5), start_year (default current year), and both growth rates are fully documented with units and defaults in the schema. The description only reinforces the multi-year scope and the euro currency, adding no parameter-level meaning beyond the schema. 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 (calcule) and a well-defined resource: a multi-year projection of the LMNP taxable result. It also enumerates the yearly line items produced, so an agent knows exactly what comes back. It does not explicitly differentiate itself from neighbours like get_simulation or compare_micro_bic, even though the micro-BIC comparison appears only as an output column.

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 explicit when-to-use statement, no prerequisites, and no routing to alternatives such as compare_micro_bic for a standalone comparison or get_simulation for a one-off scenario. Usage must be inferred from the name and the enumerated output fields.

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