Skip to main content
Glama

dev_tools_unit_convert

[$x402 pago por llamada] Convierte un valor entre unidades de la misma categoría.

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

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
valueYes
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the x402 per-call payment model, which is meaningful behavioral context. However, it does not say what happens for unsupported/cross-category units, whether unit names are case-sensitive or aliased, or what the response looks like — though the schema's x_payment field already covers the 402 flow.

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?

A single purpose sentence plus a billing tag — no waste. The payment tag is placed before the purpose, slightly delaying the actual function, which is the only structural nit.

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?

For a 4-parameter conversion tool with no annotations, no output schema, and low schema coverage, the description is too thin: it omits supported unit categories, identifier format, and result format. Only the payment notice is adequately covered.

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 only 25% (only x_payment documented), so the description must compensate and largely fails: 'from' and 'to' are bare strings with no enum, examples, or accepted identifier format. The one useful addition is the 'misma categoría' constraint on the pair, but an agent still cannot know whether to pass 'km', 'kilometers', or 'KM'.

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 ('Convierte un valor entre unidades de la misma categoría'), which lets an agent distinguish it from siblings like dev_tools_calculate (arithmetic) or img_tools_convert (image formats). It stops short of naming supported categories/units, which is the key scoping detail for a converter.

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, when-not-to-use, or alternative routing is given; the only selectivity signal is the implicit 'same category' constraint. An agent facing a km→miles task can guess, but nothing tells it how this differs from dev_tools_calculate for edge cases or what to do for cross-category input.

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.

Resources