FreeDailyPro Calculators

convert_temperature

Read-onlyIdempotent

Unit converter (temperature)

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>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "convert_temperature"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	To: one of C, F, K.
`from`	Yes	From: one of C, F, K.
`value`	Yes	The number to convert, for example: 12.5.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 13, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / from / description
```
Added value: +"From: one of C, F, K."
```
- addedInput schema / properties / to / description
```
Added value: +"To: one of C, F, K."
```
- addedInput schema / properties / value / description
```
Added value: +"The number to convert, for example: 12.5."
```
First observedOct 24, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context of its own: nothing about rounding/precision, invalid-scale handling, or return shape. It does not contradict the annotations, but contributes nothing beyond them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

There is zero wasted wording, but the definition is undersized rather than concise: a four-word fragment carries no front-loaded statement of behavior. Brevity here comes at the cost of information, not from efficiency.

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?

For a simple three-parameter conversion tool with full schema coverage, complete enums, and read-only annotations, the description is minimally sufficient to call correctly. It omits precision/rounding behavior and any indication of the return value, which are the remaining gaps an agent might care about.

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%, with enums for from/to and an example value in the schema, so the baseline is 3. The description adds no meaning beyond the schema—no note on whether values are rounded, clamped at absolute zero, or interpreted as strings/numbers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Unit converter (temperature)" restates the tool name rather than stating a specific verb and resource; there is no verb at all. An agent learns only what the name already tells it, and nothing about scope such as supported scales or precision.

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?

No when-to-use or when-not-to-use guidance is given. Siblings like convert_length and convert_weight sit in the same family, and the parenthetical "temperature" is the only implicit hint at routing, with no explicit alternative named.

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?