Skip to main content
Glama
Sign In

MaCalculatriceEnLigne

by io.github.tresor4k
OverviewDiscussionsAdmin

Calculate Notary Fees Detailed

calculate_notary_fees_detailed
Read-onlyIdempotent

Detailed breakdown of French notary fees by component (taxes, emoluments, debours). Use for property buyers in France. Inputs: property price, type (new/old). DMTO on old property = 6.32% (departmental 5.00% + communal 1.20% + 2.37% fee on the departmental part; 5.81% for first-time buyers of a main residence or departments at 4.50%). Returns total fees and per-component breakdown. See list_bundles for related 'finance-france' calculators.

Input Schema

NameRequiredDescriptionDefault
typeYesProperty type
property_priceYesProperty price EUR

Output Schema

NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / department
      Removed value: -{
-  "description": "French department code (optional, affects DMTO rate)",
-  "type": "string"
-}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish the safe read-only, idempotent profile. The description adds real behavior beyond them: it discloses the return shape (total fees plus per-component breakdown) and the DMTO rate logic including the first-time-buyer reduction. This is meaningful computational context the annotations cannot carry.

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 purpose, then inputs, then return value, then cross-reference. The parenthetical DMTO rate breakdown is dense and somewhat verbose, but it earns its place as domain-specific pricing detail rather than filler.

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?

An output schema exists, so the description need not detail return values, and it doesn't over-explain. Combined with the rate logic and the reference to list_bundles for related calculators, an agent has enough to invoke it correctly; the only gap is lack of explicit sibling routing.

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 the two parameters are already documented. The description restates 'property price, type (new/old)' but does add the non-obvious semantic link that 'type' drives the DMTO rate (old vs new), which is marginal extra value over the schema.

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+resource ('Detailed breakdown of French notary fees by component') and enumerates the components (taxes, emoluments, debours), so the agent knows exactly what it computes. It implicitly distinguishes itself from the simpler 'calculate_notary_fees' sibling via 'Detailed', but never names that sibling directly.

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?

'Use for property buyers in France' gives a clear domain context, but there is no explicit when-to-use-vs-alternative guidance. Given the nearby 'calculate_notary_fees' tool, an agent gets no rule for choosing the detailed vs. non-detailed variant.

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

All MaCalculatriceEnLigne toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources