r0x-os

Check token price

price

Fetch the current USD value for ETH or USDG. Costs $0.01 USDG per call.

Instructions

Current USD price for ETH or USDG. Costs $0.01 USDG.

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": {
      "token": "<token>"
    },
    "name": "price"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The description discloses the $0.01 USDG cost, which is a significant behavioral trait. However, with no annotations provided, it lacks any mention of rate limits, caching, or whether the operation is read-only, though that is implied. It also does not describe the response format.

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 extremely concise with two short sentences that convey the core function and cost without any unnecessary detail. It is front-loaded and easy to parse.

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 price-check tool, the description covers the purpose and cost, but it does not specify the return type or any API-specific details like error conditions. Given no output schema, the absence of return-value information leaves a gap, though the tool is otherwise simple enough to operate.

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?

The description merely restates the enum values (ETH, USDG) already present in the schema, adding no new meaning. Since schema coverage is 0%, the description was expected to compensate, but it only repeats what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool provides the current USD price for ETH or USDG, which is a specific function that distinguishes it from sibling tools like quote or trade. The scope is explicit and immediately understandable.

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 instead of alternatives like quote or trade, nor are there exclusions or prerequisites. The description only states the purpose and cost, leaving the agent to infer usage context.

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

Deploy Server