Skip to main content
Glama

minia2a-mcp-remote

x402-forex

Forex: Forex exchange rates. 🆓 5 free trial calls per signed wallet

Input Schema

NameRequiredDescriptionDefault
toNo
baseNo
symbolsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / base / description
      Removed value: -"Base to process"
    • removedInput schema / properties / symbols / description
      Removed value: -"Symbols to process"
    • removedInput schema / properties / to / description
      Removed value: -"To to process"
  2. First observed

TDQS

C2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions '5 free trial calls per signed wallet,' which usefully signals a payment/auth constraint, but it says nothing about data freshness, rate sources, error behavior, or what the tool returns.

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

Conciseness3/5

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

The description is short and front-loads the word 'Forex,' but 'Forex: Forex exchange rates' is redundant phrasing. The free-trial sentence is compact, though the overall brevity is under-specification rather than useful conciseness.

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?

For a three-parameter financial data tool with no annotations, no parameter descriptions, and no output schema, the description is far from complete. It provides only a generic resource label and a free-trial note, leaving the agent without the semantics needed to invoke the tool correctly.

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

Parameters1/5

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

The schema has three parameters (to, base, symbols) with 0% description coverage, and the description does not explain any of them. An agent must guess the expected formats and meanings of base and symbols, or whether 'to' is an alternative to 'symbols.'

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 repeats the tool name with 'Forex: Forex exchange rates,' which is essentially a tautological restatement rather than a specific verb-plus-resource explanation. It does not distinguish this tool from numerous siblings like x402-currency-rate, x402-fx-snapshot, x402-currency-convert, or x402-ecb-rates.

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 versus the many other currency and FX tools in the sibling list. The only contextual note is the free trial limit, which does not help an agent choose between alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.