MaCalculatriceEnLigne

calculate_sci_is_vs_ir

Compare SCI taxation under IS (corporate tax) vs IR (income tax). Use for French real-estate investors choosing tax regime. Inputs: rental income, charges, owner tax bracket. Returns net result under each regime. See list_bundles for related 'immobilier' calculators.

Input Schema

TableJSON Schema

Name	Required	Description
`annual_rent`	Yes	Annual gross rental income in EUR
`annual_charges`	Yes	Annual deductible charges in EUR (management fees, interest, maintenance)
`property_value`	Yes	Property value for amortization calculation under IS
`marginal_tax_rate_pct`	Yes	Shareholder marginal income tax rate in percent (e.g. 30, 41, 45)

Output Schema

TableJSON Schema

Name	Required	Description
`result`	No	Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
`source`	No	Authoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
`formula`	No	Human-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
`reference_url`	No	Link to a calcul2 page documenting the calculation in detail.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 13, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must bear full burden. It only states it returns net results but does not disclose assumptions, limitations, or social contributions. It lacks depth for a financial calculation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise with two sentences covering purpose, use case, inputs, output, and a pointer to related tools. Every sentence serves a purpose without redundancy.

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?

Given the complexity of tax calculations, the description is minimally adequate. It references list_bundles for related tools but does not explain the output format beyond 'net result.' With an output schema, return values need not be detailed, but the description still misses key input context.

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?

Schema coverage is 100%, but the description omits the 'property_value' parameter in its summary, listing only rental income, charges, and tax bracket. This is misleading and adds no value beyond the schema.

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

Purpose5/5

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

The description clearly states it compares SCI taxation under IS vs IR for French real-estate investors, specifying inputs and output. It distinguishes from sibling tools by targeting SCI and referencing related calculators.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the use case (French real-estate investors choosing tax regime) and hints at related tools via list_bundles. However, it does not explicitly exclude other scenarios or compare to direct siblings like calculate_french_income_tax.

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

All MaCalculatriceEnLigne tools Inspect

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.