Skip to main content
Glama
Sign In
r0x-os

r0x-os

by nhevers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a swap price quote

quote

Get live Uniswap V3 swap price quotes for any token pair on Robinhood Chain using ETH, USDG, or ERC20 addresses. No transaction constructed—only a $0.01 USDG fee.

Instructions

Live Uniswap V3 swap price quote for any token pair on Robinhood Chain — pass "ETH", "USDG", or any ERC20 address, no transaction constructed. 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": {
      "tokenIn": "<tokenIn>",
      "tokenOut": "<tokenOut>",
      "amountIn": "<amountIn>"
    },
    "name": "quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenInYes"ETH", "USDG", or any ERC20 token address
amountInYesAmount of tokenIn as a decimal string, e.g. "0.1"
tokenOutYes"ETH", "USDG", or any ERC20 token address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses key behavioral traits: it is live, non-transactive ('no transaction constructed'), and incurs a cost of $0.01 USDG. This goes beyond simple purpose and helps the agent understand safety and side effects, though it doesn't cover return format or error behavior.

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 a single, information-dense sentence that front-loads the purpose, then adds cost and non-transaction behavior. Every word earns its place with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple quote tool with no output schema, the description covers the essential context: chain, token formats, cost, and non-execution. It does not specify the exact response shape, but 'swap price quote' implies the returned value. Given the tool's simplicity and the schema covering parameters, this is sufficiently complete, though a mention of output would push it to 5.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds only minimal clarification by repeating the accepted token formats ('ETH', 'USDG', or ERC20 address'), which the schema already documents. It does not add meaningful new meaning beyond the schema.

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 the tool provides a 'Live Uniswap V3 swap price quote for any token pair on Robinhood Chain', which specifies the verb (get/quote), resource (swap price quote), and scope (Uniswap V3, Robinhood Chain). It also differentiates from siblings like 'trade' by explicitly noting 'no transaction constructed'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use the tool: for getting a quote rather than executing a transaction. It states 'no transaction constructed', which implicitly tells the agent this is the quoting alternative to a trade tool. However, it does not explicitly name alternatives or provide exclusion criteria, so it stops short of full usage guidance.

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

Deploy Server

Other Tools