Skip to main content
Glama
Sign In
grid402-mcp

grid402-mcp

by oliveiratc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

grid402_indicators

Fetch official Selic, CDI, and IPCA rates from Banco Central and IBGE for reliable Brazilian economic analysis and reporting.

Instructions

Consulta taxas oficiais Selic meta e diária, CDI anual e diário, IPCA acumulado 12m e mensal do Banco Central e IBGE.

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_hashNoHash opcional de transação na Base Mainnet comprovando o pagamento de 0.0005 USDC caso não utilize liquidação automática.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and it discloses almost nothing: no statement that this is a read-only lookup, no return shape, no freshness/latency of the published rates. Critically, it never mentions that access may require a 0.0005 USDC payment on Base Mainnet, which is the only behavioral detail the schema hints at.

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?

A single front-loaded sentence listing the data sources with no filler or redundancy. It is efficient, though its terseness is part of why behavioral and usage context are absent.

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 zero-required-parameter data lookup with no output schema, the description does identify what data comes back, which is the main thing needed. It leaves out the payment requirement and any indication of result structure or rate vintage, which matter given the paid-access model.

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?

There is a single optional parameter and the schema description coverage is 100%, so the schema already explains payment_tx_hash and the USDC amount in detail. The description adds nothing about it, which is acceptable at this coverage level, giving the baseline score.

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 a concrete verb of sorts ("Consulta") plus a precise set of resources: Selic meta and daily, annual and daily CDI, and 12-month and monthly IPCA, with the issuing sources (Banco Central, IBGE). An agent can tell this is a Brazilian official-rates lookup and distinguish it from siblings like grid402_forex or grid402_crypto, though it never explicitly contrasts itself with them.

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 call this rather than grid402_forex, grid402_summary, or other siblings, and no mention of prerequisites or the payment flow. The agent must infer the usage scenario entirely from the list of rate names.

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

Deploy Server

Other Tools