calculator

volume_conversion

volume_conversion

Convert volume measurements between different units like liters, gallons, cubic meters, and milliliters. Enter a value with source and target units to get accurate conversions.

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": "volume_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.4/5.0

Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. It doesn't mention what units are supported, whether the conversion is bidirectional, precision considerations, error handling, or what the output format will be. This is inadequate for a tool with 3 parameters and no output schema.

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. There's no wasted language or unnecessary elaboration, making it appropriately concise for a simple conversion tool.

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

Completeness1/5

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

Given the tool has 3 parameters with 0% schema coverage, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what units are supported, how to specify them, what the output looks like, or any behavioral aspects. This leaves the agent with insufficient information to use the tool correctly.

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

Parameters1/5

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

The schema has 0% description coverage, so all 3 parameters are undocumented in the schema. The description provides no information about what 'value', 'from_unit', or 'to_unit' should contain, what units are valid, or any format requirements. It fails to compensate for the complete lack of schema documentation.

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 as converting between volume units, which is a specific verb+resource combination. However, it doesn't differentiate from its sibling 'area_conversion' or other conversion tools, which would require mentioning it's specifically for volume units rather than area or other types.

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 provides no guidance on when to use this tool versus alternatives. With sibling tools like 'area_conversion', 'length_conversion', and 'temperature_conversion', there's no indication that this is specifically for volume units or when volume conversion is needed versus other unit types.

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

Deploy Server