Open Economics

Query official ANP fuel prices

get_anp_fuel_prices

Read-onlyIdempotent

Retrieve auditable fuel and GLP price statistics calculated from official ANP station observations. Omit year and month for the rolling latest four weeks, or provide both for a published monthly file from 2023 onward. Results retain period, product, geography, unit, sample count, source URL, and the disclosed aggregation method while excluding station identity and addresses.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	No	Published source year; provide with month for a monthly file.
`limit`	No	Maximum aggregate rows to return.
`month`	No	Published source month; provide with year for a monthly file.
`state`	No	Two-letter Brazilian state code when geography is state or municipality.
`period`	No	Reporting period granularity.	week
`product`	No	Exact ANP product label, for example GASOLINA or ETANOL.
`geography`	No	Geographic aggregation level.	country
`dataset_id`	Yes	The official ANP fuel-prices dataset identifier.
`fuel_group`	Yes	ANP product group to retrieve.
`municipality`	No	Municipality name when geography is municipality.

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.

Changed10 schema fields changedSep 11, 2026

addedInput schema / properties / dataset_id / description

Added value: +"The official ANP fuel-prices dataset identifier."

addedInput schema / properties / fuel_group / description
```
Added value: +"ANP product group to retrieve."
```
addedInput schema / properties / geography / description
```
Added value: +"Geographic aggregation level."
```

addedInput schema / properties / limit / description

Added value: +"Maximum aggregate rows to return."

addedInput schema / properties / month / description

Added value: +"Published source month; provide with year for a monthly file."

addedInput schema / properties / municipality / description

Added value: +"Municipality name when geography is municipality."

addedInput schema / properties / period / description
```
Added value: +"Reporting period granularity."
```

addedInput schema / properties / state / description

Added value: +"Two-letter Brazilian state code when geography is state or municipality."

addedInput schema / properties / year / description

Added value: +"Published source year; provide with month for a monthly file."

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/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds real behavioral context: results are auditable aggregates that deliberately exclude station identity and addresses while retaining sample count and source URL, which signals a privacy-conscious aggregation layer rather than raw observations.

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-loaded with purpose then usage then return shape. Each sentence carries distinct information (what, when, what comes back) with no repetition of structured fields.

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?

For a 10-parameter tool with an output schema present, the description covers the key conditional logic (year/month pairing) and the aggregation/privacy posture, leaving per-field syntax to the 100%-covered schema. Nothing an agent needs to call it correctly is missing.

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%, so the baseline is 3, but the description adds meaningful semantics beyond the schema: the year/month coupling (both-or-neither) and the meaning of the default (rolling latest four weeks, published monthly files from 2023). That goes past the per-field descriptions.

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?

States a specific verb (retrieve) and resource (auditable fuel and GLP price statistics) with the source qualifier (official ANP station observations). This is clearly distinguishable from sibling dataset tools like get_bcb_series or get_comexstat_data by domain.

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?

Gives explicit conditional usage: omit year and month for the rolling latest four weeks, or provide both for a published monthly file from 2023 onward. It does not name sibling tools as alternatives, but the domain is distinct enough that routing is unambiguous.

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.