Skip to main content
Glama
OpenLMNP

OpenLMNP

Compare Micro Bic

compare_micro_bic
Read-only

Compare micro-BIC and actual-expense tax regimes for a fiscal year, calculate taxable income under each, and show which is advantageous for furnished rentals.

Instructions

Compare le régime micro-BIC et le régime réel pour une année fiscale. Calcule le résultat imposable dans chaque régime et indique lequel est le plus avantageux. L'abattement micro-BIC est de 50 % pour les meublés classés, 30 % pour les non classés (loi Le Meur 2026). Tous les montants sont 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": "compare_micro_bic"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesAnnée fiscale (ex : 2025)
abatement_rateNoTaux d'abattement micro-BIC en % (50 pour une location de longue durée ou un meublé de tourisme classé, 30 pour un meublé de tourisme non classé). Défaut : 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.1
    • addedInput schema / properties / abatement_rate / description
      Added value: +"Taux d'abattement micro-BIC en % (50 pour une location de longue durée ou un meublé de tourisme classé, 30 pour un meublé de tourisme non classé). Défaut : 50"
    • addedInput schema / properties / year / description
      Added value: +"Année fiscale (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?

With readOnlyHint=true already supplied, the description adds real context: it computes a taxable result in BOTH regimes and returns an advantage indicator, and it pins the abatement figures to a legal basis (loi Le Meur 2026). It also states the unit of all amounts (euros), which prevents misreading of results. It does not describe output shape or rounding beyond that.

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?

Four short sentences that lead with the action, then the outcome, then the domain constants, then the unit convention. Nothing is redundant, though the abatement-rate sentence partially duplicates the schema field description.

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 two-parameter read-only computation with no output schema, the description covers what is calculated, what is returned in qualitative terms (the more favorable regime), the legal abatement basis, and the currency. The absence of output schema means a hint at result structure would help, but nothing essential is missing.

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%, so both parameters are already documented in the schema itself. The description echoes the 50%/30% abatement values and adds the legal reference, but contributes no new syntax or default-handling semantics beyond what the schema states. Baseline 3 applies when the schema carries the load.

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 gives a precise verb and object set ('Compare le régime micro-BIC et le régime réel') plus the scope constraint (une année fiscale), so an agent knows exactly what is computed. It does not name a sibling such as compute_fiscal_year to distinguish itself, which is why it falls short of a 5.

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?

The use case is implied by 'indique lequel est le plus avantageux', so an agent can infer the tool answers a regime-arbitrage question. However, there is no explicit when-to-use/when-not statement and no alternative tool is referenced, leaving guidance inferred rather than stated.

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