Skip to main content
Glama

Grid402 — Brazil Public Data & Network Oracle

grid402_indicators

Read-onlyIdempotent

Official BCB/IBGE macro indicators: Selic target/daily, CDI and IPCA 12m (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_indicators"
  }
}

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds meaningful context in the credit cost (0.0050 USDC / 1 credit), but says nothing about whether values are latest-snapshot or series history, nor about 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 tight sentence that front-loads the data returned and puts the price at the end. No redundancy; 'Official' is the only mild filler, though it usefully signals data provenance.

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?

There is no output schema, so the description should clarify what is returned - latest value versus time series, units, or as-of date. Given there is no date parameter, the omission leaves an agent guessing about granularity, which is a real gap for a data-retrieval tool.

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% and the single payment_tx_hash parameter is documented in detail, including accepted forms (txHash, Session Pass token, EIP-3009 payload, demo). The description adds nothing about payment or auth, so 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 specific data domain (Official BCB/IBGE macro indicators) and enumerates the series returned: Selic target/daily, CDI and IPCA 12m. That is enough to separate it from siblings like grid402_forex or grid402_global_markets, though it never states an explicit retrieval verb and relies on the name to supply it.

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?

Usage is only implied by the content list - an agent can infer this is the tool for Brazilian benchmark rates and inflation. There is no explicit when-to-use or when-not, and no mention of when grid402_forex or grid402_market_snapshot would be preferred instead.

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.