Skip to main content
Glama
Ingredient Convert MCP

Ingredient Convert MCP

fraction_to_decimal

Read-onlyIdempotent

Converts recipe fractions such as '1/2' or '1 1/2' and plain numbers into decimal amounts for ingredient measurements.

Instructions

Convert a fraction string used in recipes ('1/2', '1 1/2', '3/4') or a plain number into a decimal amount.

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": {
      "value": "<value>"
    },
    "name": "fraction_to_decimal"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesFraction string like '1/2' or '1 1/2', or a plain number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds the useful fact that both mixed fractions and plain numbers are accepted, but says nothing about invalid-input behavior or whether output is rounded.

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?

One sentence, front-loaded with the verb and resource, with inline examples that cost little and clarify accepted input. 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?

For a single-parameter, side-effect-free conversion tool with a fully documented schema, the description covers what is needed to call it correctly. The only gap is the precise return form (number vs. string, rounding), which is not covered by an output schema.

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% and the single 'value' parameter is already documented with examples in the schema. The description repeats the same format examples ('1/2', '1 1/2', '3/4') without adding constraints such as negative values, decimals, or unit handling, so the baseline 3 applies.

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 a specific verb and transformation: convert a fraction string into a decimal amount, with concrete accepted formats ('1/2', '1 1/2', '3/4'). It is clear what the tool does, though it never names its inverse sibling decimal_to_fraction, so differentiation relies on the agent inferring direction from the name.

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?

There is no when-to-use guidance, no statement of when not to use it, and no pointer to decimal_to_fraction for the reverse operation. The recipe context implies the domain, but the agent is left to infer which of the sibling conversion tools to pick.

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