FreeDailyPro Calculators

converters_units

Read-onlyIdempotent

Unit converter: 14 categories and over 130 units with exact factors

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": {
      "category": "<category>",
      "value": "<value>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "converters_units"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Unit id to convert to.
`from`	Yes	Unit id to convert from, for example gal_us, km_h, psi, kwh (see units-list for the ids and aliases).
`value`	Yes	The number to convert.
`category`	Yes	length, weight, temperature, volume, area, speed, pressure, energy, power, time, data_transfer, angle, fuel_economy or cooking. List the units of each with /v1/converters/units-list.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful scope and precision ('exact factors'), but does not disclose return format, error behavior, or other operational details; no contradiction exists.

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 a single front-loaded sentence with no filler. Every phrase contributes scope or precision: category count, unit count, and exact conversion factors.

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?

The input schema fully describes all required parameters and the annotations cover safety behavior, so the brief description is largely sufficient. It could still mention the return value or point to units-list, but those gaps are minor given the structured data.

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 the schema itself fully documents all four required parameters. The description adds no parameter-level meaning beyond the schema, making the baseline score of 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 clearly states the resource and scope: a unit converter with 14 categories, 130+ units, and exact factors. It does not differentiate itself from specific siblings such as convert_length or convert_weight, so it stops short of a 5.

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?

The description states only what the tool does, not when to use it versus alternatives. No routing guidance is given for sibling tools like convert_length, convert_temperature, or converters_units_list, even though the schema mentions units-list.

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

All FreeDailyPro Calculators 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.

Resources

Need Help?