MaCalculatriceEnLigne

calculate_child_support

Estimate French child support (pension alimentaire) based on income, custody and number of children. Returns: {income, rate_pct, monthly_support, annual_support}. See list_bundles for related 'finance-france' calculators.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`income`	Yes	Net monthly income of the paying parent in euros
`custody`	No	Custody type: full (garde principale), alternating (alternee), reduced (visite et hebergement)	full
`children_count`	Yes	Number of children (1-6)

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

A4.2/5.0

Behavior3/5

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

No annotations provided. Description gives output structure but lacks details on assumptions, legal basis, or behavior beyond 'estimate'.

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?

Two sentences with no wasted words: first sentence states purpose and inputs, second covers output and related tools.

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?

Description lists output fields, making it complete for a calculation tool. Context signals show high schema coverage, and no further detail is needed.

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

Parameters4/5

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

All parameters have schema descriptions, and the description summarizes the key inputs and output, adding 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 estimates French child support using specific inputs (income, custody, children count) and outputs relevant fields. It is a unique purpose among many sibling 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?

The description indicates French context and mentions related calculators via 'list_bundles', but does not explicitly state when not to use or compare to siblings.

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.