Skip to main content
Glama
OpenLMNP

OpenLMNP

Compute Tva

compute_tva
Read-only

Calculate the annual VAT return for VAT-liable furnished rental properties, returning collected and deductible VAT plus the balance payable or refundable by property, rate, and quarter.

Instructions

Calcule la déclaration de TVA pour les biens para-hôteliers assujettis (régime TVA liable) sur une année donnée. Retourne la TVA collectée, déductible et le solde à payer ou à récupérer, ventilés par bien, par taux et par trimestre. 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": "compute_tva"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesAnnée fiscale pour la déclaration TVA (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 pour la déclaration TVA (ex : 2025)"
  2. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, consistent with a pure computation. The description adds useful output context — collected VAT, deductible VAT, and the payable/recoverable balance, broken down by property, rate and quarter, in euros — but says nothing about rounding, regime edge cases, or what happens when no liable property exists for the year.

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?

Two sentences, front-loaded with the purpose and followed by the return content; no filler. The parenthetical '(régime TVA liable)' mixes languages and slightly obscures the regime qualifier without adding precision.

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?

No output schema exists, and the description does compensate by enumerating the returned figures and their breakdowns. Still, for a fiscal calculation tool it omits preconditions and failure modes (missing properties, non-liable entities), leaving gaps an agent would likely need to discover by trial.

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 fully documented in the schema itself. The description only echoes the notion of a fiscal year, adding no format constraints, supported range, or default behavior beyond what the schema already conveys.

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: computing the VAT declaration for para-hotel properties subject to VAT for a given year. It does not, however, distinguish itself from potentially overlapping siblings such as generate_tax_return or compute_fiscal_year, so an agent must infer the boundary.

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 only implied by the domain scoping ('biens para-hôteliers assujettis', 'une année donnée'). There is no explicit when-to-use statement, no prerequisite conditions (e.g. properties must be registered under the liable VAT regime), and no pointer to an alternative tool for other tax computations.

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