MaCalculatriceEnLigne

calculate_fraction_operations

Add, subtract, multiply, or divide two fractions and return the simplified result. Use for math homework. Inputs: num1/den1, op, num2/den2. Returns result fraction (lowest terms). See list_bundles for related 'math' calculators.

Input Schema

TableJSON Schema

Name	Required	Description
`den1`	Yes	Denominator of first fraction
`den2`	Yes	Denominator of second fraction
`num1`	Yes	Numerator of first fraction
`num2`	Yes	Numerator of second fraction
`operation`	Yes	Operation to perform

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

C2.9/5.0

Behavior2/5

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

No annotations present. Description only states it returns simplified result. No mention of side effects, permissions, or other behavioral traits. Minimal disclosure.

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?

Two sentences, concise and to the point. Could benefit from a clearer structure separating purpose from usage.

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?

With output schema present, return info is covered. Description explains operation and simplification, but lacks usage context and behavioral details. Adequate but not thorough.

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?

Input schema has 100% description coverage, so description adds little beyond listing parameters. Baseline 3 is appropriate.

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?

Clearly states the tool performs arithmetic operations on two fractions and returns simplified results. Mentions use case 'math homework', but does not explicitly differentiate from siblings beyond referencing list_bundles.

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

Usage Guidelines2/5

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

Only says 'Use for math homework', which is vague. No guidance on when not to use or alternatives, except a weak pointer to list_bundles.

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.