Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-celsius-to-kelvin

Celsius To Kelvin: Convert Celsius to Kelvin. 🆓 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-celsius-to-kelvin"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueNo
celsiusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / celsius / description
      Removed value: -"Celsius to process"
    • removedInput schema / properties / value / description
      Removed value: -"Value to process"
  2. First observed

TDQS

C2.6/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 behavioral burden. It does disclose one real trait, the free-trial quota tied to a signed wallet, but says nothing about output format or precision, valid input ranges, error behavior, or how the two input parameters interact.

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

Conciseness3/5

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

The text is short and front-loaded, but the first clause merely restates the tool name verbatim before repeating the same conversion statement, and the emoji/promo tail is noise for tool selection. Acceptable length, some redundancy.

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 tool with no annotations, no output schema, and completely undocumented parameters, the description should at minimum pin down the input parameter choice and the returned value format. It leaves the duplicate-parameter ambiguity and output shape entirely unexplained.

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% and neither parameter (value, celsius) is explained in the description. Worse, both are optional and appear to overlap, so an agent cannot tell from the description which one to populate or whether both are expected.

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 Celsius to Kelvin. The name and description together are unambiguous about what the operation does, though they never distinguish this from sibling temperature tools such as x402-temperature-convert or x402-celsius-to-fahrenheit.

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 when-to-use guidance, no mention of alternatives for general temperature conversion, and no statement of when this tool is not appropriate. The only guidance-like content is the payment note ('5 free trial calls per signed wallet'), which is about billing, not selection.

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.