Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

volume_convert

Convert volume units: litres, millilitres, cubic metres, gallons, pints and fluid ounces. Pure CPU, instant.

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": "volume_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget unit
fromNoSource unit
valueYesValue

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed4 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Source unit",
+  "type": "string"
+}
    • addedInput schema / properties / to
      Added value: +{
+  "description": "Target unit",
+  "type": "string"
+}
    • addedInput schema / properties / value
      Added value: +{
+  "description": "Value",
+  "type": "number"
+}
    • addedInput schema / required
      Added value: +[
+  "value"
+]
  4. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. 'Pure CPU, instant' usefully signals no network calls, no side effects, and deterministic fast execution, but nothing is said about error behavior for unsupported units, or about the fact that 'from' and 'to' are optional (only 'value' is required), which leaves the default-unit behavior completely undocumented.

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?

Two short sentences, front-loaded with the verb and unit set, with the performance note last. No filler or redundancy.

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 this covers the essentials, but there is no output schema and no annotations, so the description should at least mention the return value (numeric value plus unit string?) and rounding behavior, plus what happens when from/to are omitted. Those omissions are the main remaining gaps.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds the actual set of accepted units for 'from'/'to', which the schema does not supply (no enums, generic 'Source unit'/'Target unit' labels). It stops short of listing accepted spellings/abbreviations or the default units, so it does not fully compensate.

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?

States a specific verb and resource ('Convert volume units') and enumerates the supported units, which is more concrete than most siblings. However, it never distinguishes itself from the many overlapping conversion tools in the sibling list (unit_convert, convert_units, distance), leaving the agent to guess among near-duplicates.

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?

Usage is only implied by the tool name and unit list; there is no statement of when to prefer this over unit_convert or convert_units, no exclusions, and no prerequisites. With a dense family of conversion siblings, this is a real routing gap.

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

All GadgetHumans API Hub toolsInspect
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