Scientific Calculator

Mixed Fraction Calculator

calculator_mixed_fraction

Read-only

Use this tool to convert mixed numbers to improper fractions, improper fractions to mixed numbers, or simplify fractions. Examples: 2 1/3 → 7/3; 7/3 → 2 1/3.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "conversion": "<conversion>",
      "numerator": "<numerator>",
      "denominator": "<denominator>"
    },
    "name": "calculator_mixed_fraction"
  }
}

Input Schema

Name	Required	Description
`whole`	No	Whole part for mixed_to_improper (e.g., 2 in 2 1/3).
`numerator`	Yes	Numerator of the fractional part.
`conversion`	Yes	Conversion type: mixed_to_improper, improper_to_mixed, or simplify.
`denominator`	Yes	Denominator of the fractional part.

Output Schema

Name	Required	Description	Default
`whole`	No
`result`	Yes
`numerator`	Yes
`conversion`	Yes
`expression`	Yes
`denominator`	Yes
`result_numerator`	Yes
`result_denominator`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds example transformations but says nothing about failure behavior (e.g., zero denominator, or whether 'whole' is needed for mixed_to_improper), which is the remaining behavioral gap.

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, front-loaded with the core purpose, followed by compact examples that demonstrate each conversion. Nothing is redundant or padded.

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?

An output schema exists, so return values need no explanation, and the annotations cover safety. The one gap is that 'whole' is optional in the schema yet essential for mixed_to_improper, which the description never clarifies.

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 description coverage is 100%, so each parameter is already documented, including the enum values for 'conversion'. The description's examples illustrate the mapping but add no syntax beyond what the schema already states, making the baseline 3 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?

The description names three concrete operations (mixed-to-improper, improper-to-mixed, simplify) with worked examples, so the agent knows exactly what the tool computes. It does not explicitly distinguish itself from neighboring siblings like calculator_fraction or calculator_simplify, which handle overlapping fraction territory.

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?

'Use this tool to convert...' gives clear context, and the two examples show the intended input/output shapes. There are no exclusions, so an agent choosing between this and calculator_simplify or calculator_fraction gets no guidance on which to prefer.

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

All Scientific Calculator 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.