Skip to main content
Glama
Sign In

Axiom Works AgentReader

by io.github.grokbot1233
OverviewDiscussionsAdmin

fx_rates

Use this for official ECB currency exchange rates (~30 fiat incl GBP/EUR/USD/JPY), latest or a historical date (YYYY-MM-DD), with optional amount conversion. $0.002 USDC.

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": "fx_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNo
dateNo
amountNo
symbolsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two genuinely useful traits beyond structured data: the data source (official ECB) and the cost ($0.002 USDC). It does not say what the response looks like, whether a non-trading day rolls back to the prior fixing, or how errors are surfaced, which is a meaningful gap for an unannotated tool.

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?

One compact sentence front-loads the purpose, then layers scope, modes, and price with zero filler. Every clause (source, currency count, date format, conversion, cost) carries information an agent needs.

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 four-parameter, non-annotated, no-output-schema tool, the description covers the main calling modes and cost but omits default behavior when base/symbols are omitted (all parameters are optional) and any hint at the returned structure. It is enough to attempt a call but not enough to call it confidently.

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%, so the description must explain all four parameters. It clarifies the date format (YYYY-MM-DD) and that amount triggers conversion, but leaves 'base' and 'symbols' completely undefined — the base-vs-symbols distinction is the single most important semantic for an FX tool and an agent cannot infer it here.

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 names the specific resource (ECB reference exchange rates), its scope (~30 fiat currencies including GBP/EUR/USD/JPY) and its two modes (latest or historical date). The verb is implicit rather than stated ('Use this for... rates'), and no sibling tool in the list overlaps with FX, so differentiation is trivially clear.

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?

'Use this for official ECB currency exchange rates' gives implied when-to-use guidance, and the historical-date mention clarifies one usage branch. There is no statement of when NOT to use it, no alternatives for crypto pricing (e.g. token_metadata or pricing siblings), and no prerequisites or auth guidance.

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

All Axiom Works AgentReader toolsInspect
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