Open Economics

Query multidimensional IBGE data

get_ibge_data

Read-onlyIdempotent

Retrieve an explicit slice of an IBGE aggregate after inspecting its schema. Returns variables containing classification selections, geographies, and observations; official suppression, missing, quality-flag, and zero states remain distinct.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`periods`	No	Recent-period shorthand such as -12, or explicit official period IDs separated by \|.	-12
`locality`	No	BR or an explicit IBGE geography selection such as N3[35].	BR
`variable`	Yes	One or more official variable IDs separated by \|.
`dataset_id`	Yes	Exact IBGE aggregate ID returned by search_official_data.
`classification`	No	Explicit classification selections from the schema, such as 11255[90707].

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Source-preserving data or schema payload for the selected official dataset.
`meta`	Yes	Response metadata and source provenance.
`links`	No	Related API links.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 11, 2026

addedInput schema / properties / dataset_id / description

Added value: +"Exact IBGE aggregate ID returned by search_official_data."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "description": "REST-aligned Open Economics response with data, metadata, links, and source provenance.",
+  "properties": {
+    "data": {
+      "description": "Source-preserving data or schema payload for the selected official dataset."
+    },
+    "links": {
+      "additionalProperties": {},
+      "description": "Related API links.",
+      "properties": {
+        "observations": {
+          "description": "Canonical observations endpoint for this dataset.",
+          "type": "string"
+        },
+        "self": {
+          "description": "Canonical URL for this response.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "meta": {
+      "additionalProperties": {},
+      "description": "Response metadata and source provenance.",
+      "properties": {
+        "dataset": {
+          "description": "Open Economics dataset identity when supplied."
+        },
+        "provenance": {
+          "description": "Upstream source URLs, versions, timestamps, and methodology details."
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "type": "object"
+}

First observedSep 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real value beyond that by enumerating the return shape (variables with classification selections, geographies, observations) and by stating that official suppression, missing, quality-flag, and zero states remain distinct — semantics an agent would otherwise have to guess.

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?

Two dense sentences with no filler: the first front-loads the action and its prerequisite, the second enumerates output composition and state semantics. Every clause carries information.

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?

With an output schema present, the description need not detail return values, yet it still communicates the important semantic point that missing/suppressed/zero states are distinct — a common source of misinterpretation. For a five-parameter, schema-covered read tool this is largely sufficient, though it omits any note on result size or pagination limits.

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%, so all five parameters (periods, locality, variable, dataset_id, classification) are already documented with patterns and examples in the schema. The description adds only the general notion of an 'explicit slice' and does not explain period shorthand, geography nesting syntax, or the pipe-delimited multi-ID convention beyond what the schema provides. 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?

States a specific verb (Retrieve) and resource (an explicit slice of an IBGE aggregate), with the qualifier 'explicit slice' signaling that broad discovery is out of scope. Sibling differentiation is only implicit, via the reference to inspecting the schema first, rather than naming get_ibge_schema or search_official_data.

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 phrase 'after inspecting its schema' establishes a clear prerequisite workflow step and implicitly routes the agent to the schema-inspection sibling before calling this tool. No explicit when-not-to-use guidance or named alternative is given, so it falls short of the top band.

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

All Open Economics tools Inspect

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.