Synthex Forge — x402 Paid Agent Services

Get Rates Reference

get_rates_reference

Read-onlyIdempotent

What is this amount worth right now?. use it rather than create_prepaid_capacity for rates reference, not prepaid capacity; an object with 18 fields including User-Agent, as_of. $0.01 USDC.

Input Schema

Name	Required	Description
`base`	No	The base this operation operates on. See the schema for its type and whether it is required.
`quote`	No	The quote this operation operates on. See the schema for its type and whether it is required.
`symbol`	No	The symbol this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`ask`	No	The `ask` field of the response.
`bid`	No	The `bid` field of the response.
`day`	No	The `day` field of the response.
`leg`	No	The `leg` field of the response.
`via`	No	The `via` field of the response.
`base`	No	The `base` field of the response.
`rate`	No	The `rate` field of the response.
`as_of`	No	The date the answer is computed as of.
`price`	No	The `price` field of the response.
`quote`	No	The `quote` field of the response.
`rates`	No	The `rates` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`source`	No	The `source` field of the response.
`symbol`	No	The `symbol` field of the response.
`verdict`	Yes	The decision this tool returned.
`is_stale`	No	The `is_stale` field of the response.
`User-Agent`	No	The `User-Agent` field of the response.
`staleness_seconds`	No	The `staleness_seconds` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedOct 31, 2026

addedOutput schema / properties / User-Agent

Added value: +{
+  "description": "The `User-Agent` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / as_of

Added value: +{
+  "description": "The date the answer is computed as of.",
+  "type": "string"
+}

addedOutput schema / properties / ask

Added value: +{
+  "description": "The `ask` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / base

Added value: +{
+  "description": "The `base` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / bid

Added value: +{
+  "description": "The `bid` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / day

Added value: +{
+  "description": "The `day` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / is_stale

Added value: +{
+  "description": "The `is_stale` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / leg

Added value: +{
+  "description": "The `leg` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / price

Added value: +{
+  "description": "The `price` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / quote

Added value: +{
+  "description": "The `quote` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / rate

Added value: +{
+  "description": "The `rate` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / rates

Added value: +{
+  "description": "The `rates` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / source

Added value: +{
+  "description": "The `source` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / staleness_seconds

Added value: +{
+  "description": "The `staleness_seconds` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / symbol

Added value: +{
+  "description": "The `symbol` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / verdict

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / properties / via

Added value: +{
+  "description": "The `via` field of the response.",
+  "type": "object"
+}

addedOutput schema / required

Added value: +[
+  "detail",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description does add two genuinely new behavioral facts: the response is an object with 18 fields including User-Agent and as_of, and each call costs $0.01 USDC — the pricing detail is valuable and not present in annotations. It stops short of saying where rates come from or how fresh they are.

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

Conciseness2/5

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

The text is a disjointed set of fragments — a question, a semicolon-linked comparison, an output-shape note and a price — with no front-loaded statement of function. The '$0.01 USDC' fragment in particular is unterminated context that costs reading effort without clear framing.

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?

An output schema exists, so the '18 fields including User-Agent, as_of' sentence is partly redundant, and the annotations carry the safety profile. What is missing is the core answer: what a 'rates reference' actually is, what the base/quote/symbol inputs resolve to, and what the as_of field means for freshness — for a financial reference lookup that gap is material.

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 all three parameters (base, quote, symbol) are documented in the schema and the baseline is 3. The description contributes nothing about base/quote/symbol semantics, and given the schema's own descriptions are generic boilerplate, no additional meaning is layered on.

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

Purpose2/5

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

The description is phrased as a rhetorical question ('What is this amount worth right now?') rather than a specific verb+resource statement, so the agent must infer that this returns an FX/rates reference. The only concrete signal is the contrast with `create_prepaid_capacity`, which tells you what it is not more than what it is.

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?

It does name an alternative explicitly ('use it rather than `create_prepaid_capacity`'), which is real routing guidance. However the follow-on phrase 'for rates reference, not prepaid capacity' is circular and restates the same point without adding a condition, so the agent gets a comparison but no when-to-use criteria (e.g. which currency pairs, freshness semantics).

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

All Synthex Forge — x402 Paid Agent Services 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.