Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-cm-to-inches

Cm To Inches: Convert cm to inches. 🆓 5 free trial calls per signed wallet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-cm-to-inches"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / value / description
      Removed value: -"Value to process"
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose one genuinely behavioral fact beyond the schema — the payment model of five free trial calls per signed wallet — but says nothing about what happens after the trial, rounding/precision, handling of negative or non-numeric input, or the error behavior when the wallet is unsigned.

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

Conciseness4/5

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

Two short sentences with no filler beyond the redundant name-prefix. The conversion behavior is front-loaded, though the label 'Cm To Inches:' duplicates the tool name and could be removed without loss.

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?

There is no output schema and no annotations, so the description should specify the return value (a number of inches) and its precision, plus the accepted input format. Neither is covered, leaving an agent to guess at rounding and numeric parsing for a tool whose whole job is numeric transformation.

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 coverage is 0%, so the single 'value' parameter is undocumented in structure. The description implicitly implies the parameter is the centimetre amount, but never states that it is a numeric string, whether units can be appended, whether decimals are allowed, or what format is accepted.

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 states a specific verb and resource: 'Convert cm to inches.' An agent immediately knows what the tool does, and it is distinguishable from the sibling x402-inches-to-cm by direction. The leading 'Cm To Inches:' label is a redundant restatement of the tool name, which adds nothing but does not obscure the purpose.

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?

There is no guidance on when to use this tool, no mention of the inverse sibling, and no prerequisites. The only context offered is a pricing note ('5 free trial calls per signed wallet'), which says nothing about selection between alternatives or appropriate input ranges.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.