Skip to main content
Glama
tresor4k

macalc

calculate_property_transfer_tax

Compute French property transfer tax (droits de mutation) for property buyers. Input price, department, and type to get tax due and effective rate.

Instructions

Compute French property transfer tax (droits de mutation) by department. Use for property buyers. Inputs: property price, department, type (new/old). Returns tax due and effective rate. See list_bundles for related 'immobilier' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priceYesProperty price in local currency
countryYesCountry code: FR/BE/US/UK/DE

Output Schema

TableJSON 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).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior4/5

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

No annotations provided, but description correctly indicates it's a computation tool with no destructive side effects. It mentions returns tax due and effective rate. Lacks detail on authentication or rate limits but acceptable for a calculator.

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?

Three sentences, front-loaded with purpose, no fluff. Could be more precise but concise.

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

Completeness2/5

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

Description does not align with schema, missing important parameters. Output schema exists but input confusion reduces completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description lists inputs (price, department, type) but schema only has price and country. This mismatch misleads about required parameters and reduces schema's value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states it computes French property transfer tax, but mentions inputs (department, type) not present in schema, causing confusion. Purpose is partially clear but inconsistent.

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?

Says 'Use for property buyers' and references list_bundles for related calculators, but no explicit when-to-use vs when-not or comparison with siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server