RocketChange exchange

get_quote

Read-onlyIdempotent

A quote for an exchange and the link to make it on the site.

    `give` and `receive` are method codes; `amount` is what the client gives
    (amount_side="give") or wants to receive (amount_side="receive"). Returns
    both amounts, the rate, the limits, the requisites the site will ask for
    and `exchange_link`: the site's exchange form with all this filled in,
    where the person enters the e-mail and requisites and creates the bid.

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": {
      "give": "<give>",
      "receive": "<receive>",
      "amount": "<amount>"
    },
    "name": "get_quote"
  }
}

Input Schema

Name	Required	Default
`give`	Yes
`lang`	No	en
`amount`	Yes
`receive`	Yes
`amount_side`	No	give

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, not open-world), and the description adds useful behavioral context beyond them: it enumerates the returned values (both amounts, rate, limits, requisites, exchange_link) and describes the downstream action of creating the bid on the site. It does not discuss caching, rate limits, or error cases, which keeps it below a 5.

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?

The purpose is front-loaded in the first sentence, and the following sentences add concrete detail about inputs and outputs. There is some mild redundancy and awkward indentation, but no sentence is clearly wasted.

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?

With no output schema, the description steps in to enumerate return values and the exchange-link workflow, which is exactly what an agent needs. Gaps remain around `lang` semantics and the source of valid method codes, but overall it is substantively complete for a read-only quote tool.

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 0%, so the description must carry parameter meaning. It explains `give`/`receive` as method codes and how `amount` pairs with `amount_side`, which is genuinely helpful, but it never explains the `lang` parameter or where valid method codes come from. Partial compensation only.

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 first sentence names the specific resource (a quote for an exchange) and an extra artifact (the exchange link), which clearly separates it from siblings like get_reserves or list_pay_methods. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

Usage is implied by the quote workflow ('the person enters the e-mail and requisites and creates the bid'), but there is no explicit when-to-use or when-not-to-use guidance relative to siblings such as list_receive_options. The agent must infer that this is the final quoting step after discovering methods.

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

All RocketChange exchange tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?