Skip to main content
Glama

Grid402 — Brazil Public Data & Network Oracle

grid402_market_snapshot

Read-onlyIdempotent

Consolidated Financial and Macro Snapshot (PTAX Forex + Crypto Spot + Selic/CDI/IPCA + ANBIMA) (0.0150 USDC / 3 credits).

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_market_snapshot"
  }
}

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description's real contribution is the cost disclosure (0.0150 USDC / 3 credits), which is useful per-invocation behavior an agent must budget for. It stops short of explaining whether payment is required or what a credit is, and says nothing about data freshness or return shape.

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?

One sentence, front-loaded with the resource name, with the data feeds and price grouped in parentheses. Nested parentheses and bare acronyms make it slightly dense, but there is no filler and nothing is buried.

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?

With zero required parameters, full annotation coverage and no output schema, the bar is modest, but the definition leaves real gaps: it does not say whether the call is free without a payment hash, what the snapshot's fields or refresh cadence are, or what 3 credits means in practice. Adequate to identify the tool, insufficient to call it confidently.

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% for the single payment_tx_hash parameter, and the schema text already lists the accepted forms (Base Mainnet txHash, Session Pass token, EIP-3009 base64 payload, demo). The description adds no further meaning about that parameter, so the baseline 3 applies.

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 resource precisely (a consolidated financial and macro snapshot) and enumerates its constituent data feeds: PTAX forex, crypto spot, Selic/CDI/IPCA and ANBIMA. The word 'Consolidated' implicitly separates it from the single-domain siblings grid402_forex, grid402_crypto and grid402_indicators, but that differentiation is left for the agent to infer rather than stated.

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 when-to-use guidance at all: nothing says to prefer this over grid402_forex plus grid402_crypto for a one-shot macro read, and nothing states prerequisites or eligibility. The only ancillary information is a price, which tells the agent cost but not selection criteria.

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.