MaCalculatriceEnLigne

calculate_savings_goal

Compute time and monthly contribution needed to reach a savings target. Use for goal-based personal finance. Inputs: target amount, current savings, monthly contribution, annual return %. Returns months to goal. See list_bundles for related 'finance-universal' calculators.

Input Schema

TableJSON Schema

Name	Required	Description
`annual_rate`	Yes	Annual return rate percent
`target_amount`	Yes	Savings target EUR
`monthly_savings`	Yes	Monthly savings EUR

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

B3.4/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 disclose behavior. It mentions inputs and returns months to goal but does not state the underlying formula, assumptions (e.g., starting savings assumed zero?), or edge cases. This is insufficient for a financial calculator.

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 three sentences long, front-loads the main action, and includes no fluff. Every sentence contributes value.

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?

The description claims to compute both time and monthly contribution, yet the input schema only includes monthly_savings (user-provided), not time. This inconsistency suggests incomplete specification. Also, the output schema is present but not detailed. Missing current savings parameter is a notable gap.

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%, so the schema already describes parameters. The description lists inputs but adds no additional meaning beyond that. Baseline score of 3 is appropriate.

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 computes time and monthly contribution for a savings target using personal finance goal-based inputs. It specifies inputs and outputs, and distinguishes itself from siblings by referencing a bundle.

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?

The description says 'Use for goal-based personal finance' and points to list_bundles for related calculators, but does not explicitly state when not to use this tool or how it differs from other finance calculators like calculate_compound_interest.

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.