Skip to main content
Glama

grid402_forex

Read-onlyIdempotent

Official BCB PTAX fiat exchange rates USD, EUR, GBP to BRL (0.0050 USDC / 1 credit).

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

Input Schema

NameRequiredDescriptionDefault
payment_tx_hashNoOptional txHash on Base Mainnet, Session Pass token (pass_g402_...), EIP-3009 base64 payload, or demo for Sandbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, openWorld, and non-destructive behavior, so the description need not repeat them. It adds useful source and cost context ('Official BCB PTAX', '0.0050 USDC / 1 credit') but does not explain return cadence, rate limits, or what the payment parameter enables.

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 definition is a single compact sentence with no filler; source, currencies, target, and price are front-loaded. Every element carries information relevant to selecting the tool.

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 low-complexity, no-required-parameter read tool with rich annotations and full schema coverage, the description covers source, currency scope, and cost. It still leaves return-shape/timing and sibling routing implicit, which is a meaningful gap because no output schema exists.

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?

The sole parameter, payment_tx_hash, is fully documented in the schema, so the baseline is 3. The description does not add any syntax or usage meaning beyond the schema for that optional payment field.

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 identifies a specific data resource: official BCB PTAX fiat exchange rates for USD, EUR, and GBP against BRL. It distinguishes the source and currency scope from siblings such as grid402_crypto or grid402_global_markets, though it omits an explicit retrieval verb.

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?

No when-to-use, when-not-to-use, or alternative guidance is provided. An agent must infer from 'fiat exchange rates' that this is the right tool for BCB PTAX BRL rates, with no routing advice against the many sibling data tools.

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.

Resources