Skip to main content
Glama

calendario_divulgacoes

Read-onlyIdempotent

Retrieve upcoming IBGE indicator release dates and the next Copom decision, with optional date window, start date, and title filter.

Instructions

Próximas divulgações de indicadores do IBGE e a data da próxima decisão do Copom.

Args: dias: tamanho da janela, em dias, a partir de inicio. filtro: texto para filtrar pelo título (ex.: "IPCA", "PIB", "PNAD", "industrial"). inicio: data inicial (AAAA-MM-DD); padrão: hoje. Datas passadas mostram o que já saiu.

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

Input Schema

NameRequiredDescriptionDefault
diasNo
filtroNo
inicioNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile needs no restating. The description adds genuine behavioral context beyond that — the window is measured from 'inicio', and past dates return already-released events rather than an error — but says nothing about result ordering, result volume, or how far ahead IBGE publishes its calendar.

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?

The purpose sentence is front-loaded and the parameter notes follow in a compact, scannable block. The 'Args:' framing is a docstring artifact rather than prose, but every line still carries information; nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-optional-parameter read-only tool with no output schema, this covers purpose, defaults, date format and one important edge behavior. The main omission is any hint of the returned structure (event title + date pairs) and sort order, which an agent must infer.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the full burden, and it does so credibly: it defines 'dias' as a window length measured from 'inicio' (not from today), gives the AAAA-MM-DD format and today-default for 'inicio', and illustrates 'filtro' with concrete title examples like IPCA and PNAD. Remaining gaps are minor — no case/accent sensitivity note for 'filtro' and no bounds on 'dias'.

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 resource and scope: upcoming IBGE indicator releases plus the date of the next Copom decision. That is enough to distinguish it from series/data-fetching siblings, but it never explicitly contrasts itself with the 'copom' sibling, which presumably also covers Copom scheduling.

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: it is clearly a forward-looking calendar query, and the note that past dates show what already came out hints at historical use. There is no explicit when-to-use/when-not guidance and no named alternative for pure Copom lookups or for retrieving the actual indicator values.

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