Skip to main content
Glama
Sign In

Ibge Br

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Aggregated Data

aggregated_data
Read-onlyIdempotent

Pull official IBGE/SIDRA statistical series (inflation, GDP, population, etc.). Specify the aggregate table, variable, periods, and locality. Common examples: IPCA monthly inflation = aggregate "1737" variable "63"; population estimate = aggregate "6579" variable "9324". Returns time series keyed by period.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "periods": "-1",
      "variable": "63",
      "aggregate": "1737",
      "localities": "N1[all]"
    },
    "name": "aggregated_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodsNoPeriods: "-1" (latest), "-6" (last 6), or explicit like "202604" or "202601-202604". Default "-1".
variableYesVariable id within the aggregate, e.g. "63" (IPCA monthly variation %). Use "all" for every variable.
aggregateYesSIDRA aggregate (table) id, e.g. "1737" (IPCA) or "6579" (population estimate). Discover ids via list_aggregates.
localitiesNoLocality filter, e.g. "N1[all]" (Brazil), "N3[35]" (state SP), "N6[3550308]" (a municipality). Default "N1[all]". Brackets are auto-encoded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "aggregate": "1737",
+    "localities": "N1[all]",
+    "periods": "-1",
+    "variable": "63"
+  },
+  {
+    "aggregate": "6579",
+    "localities": "N3[35]",
+    "periods": "-6",
+    "variable": "9324"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (read-only, idempotent, non-destructive). The description adds behavioral context: returns time series keyed by period and mentions auto-encoding of brackets in localities. No contradictions.

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?

Three sentences front-load the purpose, then provide examples and return format. No redundancy, every sentence earns its place.

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

Completeness5/5

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

Given full schema coverage and absence of output schema, the description is complete: explains all parameters, provides examples, and states return type (time series keyed by period).

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 coverage is 100% with descriptions and examples. The description adds further value by providing concrete examples (e.g., aggregate 1737 variable 63 for IPCA) and linking to list_aggregates, enhancing understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool pulls official IBGE/SIDRA statistical series (inflation, GDP, population). It uses specific verbs and resource references, and distinguishes itself from siblings like list_aggregates by focusing on data retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides common examples and directs users to list_aggregates for discovering aggregate IDs, offering clear usage context. However, it does not explicitly mention when not to use this tool or suggest alternatives beyond list_aggregates.

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

All Ibge Br toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources