calculator

temperature_conversion

temperature_conversion

Convert temperature values between Celsius, Fahrenheit, and Kelvin units for scientific, cooking, or weather applications.

Instructions

在摄氏度、华氏度和开尔文之间进行转换

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_unit": "<from_unit>",
      "to_unit": "<to_unit>"
    },
    "name": "temperature_conversion"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes
`from_unit`	Yes
`to_unit`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 5, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the conversion action but doesn't disclose behavioral traits like error handling (e.g., invalid units), precision, rounding, or output format. For a tool with no annotations, this leaves significant gaps in understanding how it behaves.

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, efficient sentence in Chinese that directly states the tool's function. It's front-loaded with no wasted words, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on parameter usage, error conditions, return values, and behavioral context. For a 3-parameter tool with no structured support, this is inadequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions the units involved (Celsius, Fahrenheit, Kelvin) but doesn't explain the parameters (value, from_unit, to_unit) or their semantics (e.g., valid unit strings, numeric ranges). This adds minimal value beyond the schema's property names.

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 tool's purpose: '在摄氏度、华氏度和开尔文之间进行转换' (convert between Celsius, Fahrenheit, and Kelvin). It specifies the verb (convert) and resources (temperature units), but doesn't explicitly differentiate from sibling conversion tools like area_conversion or length_conversion beyond the temperature domain.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention any prerequisites, constraints, or comparisons with other conversion tools in the sibling list. It's a standalone statement without context.

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

Deploy Server