Skip to main content
Glama
OpenLMNP

OpenLMNP

Get Simulation

get_simulation
Read-only

Compare the micro-BIC and réel regimes for a given year: gross income, taxable results, tax savings and recommendation, plus market rent benchmarks.

Instructions

Compare le régime micro-BIC et le régime réel pour une année donnée. Retourne : revenus bruts, résultats micro-BIC (50% ou 30% selon classement), résultat réel (après charges et amortissements), avantage fiscal, recommandation, et économie d'impôt estimée pour différentes TMI. Tous les montants sont en euros. Inclut aussi, à titre de simple repère et bien par bien, le loyer de marché d'une location NON MEUBLÉE (« Carte des loyers » ANIL) quand la commune du bien est connue — jamais utilisé dans le calcul ci-dessus, jamais comparable tel quel à une recette de meublé.

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_simulation"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoAnnée fiscale à simuler (défaut : année courante)
abatementNoAbattement micro-BIC : "50" pour une location de longue durée ou un meublé de tourisme classé, "30" pour un meublé de tourisme non classé

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.1
    • addedInput schema / properties / abatement / description
      Added value: +"Abattement micro-BIC : \"50\" pour une location de longue durée ou un meublé de tourisme classé, \"30\" pour un meublé de tourisme non classé"
    • addedInput schema / properties / year / description
      Added value: +"Année fiscale à simuler (défaut : année courante)"
  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?

Annotations already establish readOnlyHint=true, and the description adds real context beyond that: the units of every returned amount (euros), the enumeration of computed outputs, and an explicit caveat that the ANIL market-rent figure is an indicative benchmark for NON-MEUBLÉ housing, never used in the calculation and never directly comparable to a furnished rental receipt. This pre-empts a plausible misreading of the output, which is exactly the kind of value the description should add.

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?

Purpose is front-loaded in the first sentence and the return-field list follows in a single dense sentence. The ANIL caveat is longer than strictly necessary but it is the one piece of information most likely to prevent misuse of the output, so it earns its space.

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 carries the burden of explaining returns, and it does so field by field, including the TMI-based tax-saving estimates and a warning about the one non-comparable figure. What is missing is the relationship to the similarly named sibling, which matters for correct tool selection.

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 both `year` and `abatement` are already documented, including the '50'/'30' values. The description restates the 50%/30% rule ('selon classement') but adds no new syntax, defaults, or edge-case 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?

The description opens with a specific verb and resource: 'Compare le régime micro-BIC et le régime réel pour une année donnée', then enumerates exactly what is computed. It does not, however, differentiate itself from the sibling compare_micro_bic, which by name appears to cover the same ground, so the agent cannot resolve the overlap from the text alone.

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 statement of when to use this tool, when not to, or which sibling to prefer for a similar fiscal comparison. The only implicit cue is 'pour une année donnée', which does not help an agent choose between get_simulation and compare_micro_bic.

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