Energetica — Argentine Oil & Gas Data

Energy prices and exchange rates

query_prices

Read-onlyIdempotent

International and local energy prices: WTI, Brent, Henry Hub (daily, USD), Argentine crude price used for royalties by province (monthly, USD/bbl) and ARS/USD exchange rates (daily). Most recent first. Example: {serie: 'BRENT', fecha_desde: '2024', frecuencia: 'mensual'}.

Input Schema

Name	Required	Description
`serie`	Yes
`max_rows`	No
`provincia`	No	Only CRUDO_LOCAL; omit for every province
`frecuencia`	No	Average; CRUDO_LOCAL is monthly
`fecha_desde`	No
`fecha_hasta`	No	Inclusive

Output Schema

Name	Required	Description	Default
`meta`	Yes
`rows`	Yes
`columns`	Yes
`sections`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 19, 2026

removedInput schema / properties / fecha_desde / description

Removed value: -"Start period YYYY, YYYY-MM or YYYY-MM-DD"

changedInput schema / properties / fecha_hasta / description

Previous value: -"End period YYYY, YYYY-MM or YYYY-MM-DD, inclusive"New value: +"Inclusive"

changedInput schema / properties / frecuencia / description

Previous value: -"Aggregation (average). Default: diario for daily series; CRUDO_LOCAL is monthly"New value: +"Average; CRUDO_LOCAL is monthly"

removedInput schema / properties / max_rows / description

Removed value: -"Rows to return (default 200; capped by your tier). The result says if rows were cut."

removedInput schema / properties / max_rows / maximum
```
Removed value: -9007199254740991
```

changedInput schema / properties / max_rows / type

Previous value: -"integer"New value: +"number"

changedInput schema / properties / provincia / description

Previous value: -"Only for CRUDO_LOCAL: province. Omit to get every province"New value: +"Only CRUDO_LOCAL; omit for every province"

removedInput schema / properties / serie / description
```
Removed value: -"Price series to query"
```
addedOutput schema / properties / columns / items / properties / unit
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / meta / properties / definitions

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / meta / properties / notes

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / sections

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "columns": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "type": {
+              "type": "string"
+            },
+            "unit": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "name",
+            "type"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "name": {
+        "type": "string"
+      },
+      "rows": {
+        "items": {
+          "items": {},
+          "type": "array"
+        },
+        "type": "array"
+      },
+      "truncated": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "name",
+      "columns",
+      "rows",
+      "truncated"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed3 schema fields changedOct 19, 2026

changedInput schema / properties / frecuencia / description

Previous value: -"Frequency aggregation. Default: diario for intl prices, mensual for local"New value: +"Aggregation (average). Default: diario for daily series; CRUDO_LOCAL is monthly"

addedInput schema / properties / max_rows

Added value: +{
+  "description": "Rows to return (default 200; capped by your tier). The result says if rows were cut.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "columns": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "name": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "type"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "meta": {
+      "additionalProperties": false,
+      "properties": {
+        "max_rows": {
+          "type": "number"
+        },
+        "query_ms": {
+          "type": "number"
+        },
+        "returned": {
+          "type": "number"
+        },
+        "sources": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "sql": {
+          "type": "string"
+        },
+        "truncated": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "returned",
+        "truncated",
+        "max_rows",
+        "sources",
+        "query_ms"
+      ],
+      "type": "object"
+    },
+    "rows": {
+      "items": {
+        "items": {},
+        "type": "array"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "columns",
+    "rows",
+    "meta"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedOct 18, 2026

addedInput schema / properties / provincia

Added value: +{
+  "description": "Only for CRUDO_LOCAL: province. Omit to get every province",
+  "enum": [
+    "NEUQUEN",
+    "CHUBUT",
+    "MENDOZA",
+    "SANTA CRUZ",
+    "SALTA",
+    "RIO NEGRO",
+    "LA PAMPA",
+    "TIERRA DEL FUEGO",
+    "FORMOSA",
+    "JUJUY",
+    "ESTADO NACIONAL"
+  ],
+  "type": "string"
+}

changedInput schema / properties / serie / enum

Previous value: -[
-  "WTI",
-  "BRENT",
-  "HENRY_HUB",
-  "ESCALANTE",
-  "MEDANITO",
-  "USD_OFICIAL",
-  "USD_BLUE",
-  "USD_MEP",
-  "USD_CCL"
-]New value: +[
+  "WTI",
+  "BRENT",
+  "HENRY_HUB",
+  "CRUDO_LOCAL",
+  "USD_OFICIAL",
+  "USD_MAYORISTA",
+  "USD_BLUE",
+  "USD_MEP",
+  "USD_CCL"
+]

Changed2 schema fields changedOct 18, 2026

changedInput schema / properties / fecha_desde / description

Previous value: -"Start date YYYY-MM-DD"New value: +"Start period YYYY, YYYY-MM or YYYY-MM-DD"

changedInput schema / properties / fecha_hasta / description

Previous value: -"End date YYYY-MM-DD"New value: +"End period YYYY, YYYY-MM or YYYY-MM-DD, inclusive"

First observedApr 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description's job is supplementary. It adds genuinely useful behavior beyond the annotations: default ordering ('Most recent first') and per-series frequency/units (daily USD, monthly USD/bbl). It stays silent on max_rows defaults and pagination, which keeps it short of a 5.

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?

Three tight sentences with no filler: data inventory first, then the ordering behavior, then a concrete example. Every clause carries information, though the middle inventory sentence is dense enough that it borders on a run-on.

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, return values need no explanation, and the description covers series semantics, frequencies, currencies, and call syntax. The only real omissions are the max_rows default/limit behavior and the accepted date format outside the example, which are minor for a read-only lookup tool.

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 only 50%, so the description has to compensate, and it does for the most important parameter: it maps the bare enum values (BRENT, HENRY_HUB, CRUDO_LOCAL, USD_BLUE/MEP/CCL) to their real meaning and frequency. The example also pins the fecha_desde format. max_rows and fecha_hasta remain undocumented beyond the schema's 'Inclusive' note.

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 the specific resource and enumerates the exact series returned (WTI, Brent, Henry Hub, Argentine crude, ARS/USD rates), which makes it clearly distinguishable from siblings like query_production or query_trade. There is no explicit verb ('query'/'retrieve'), but the content coverage is specific enough that an agent knows exactly what data it yields.

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 implied rather than stated: the enumerated series and the worked example show the call shape, but there is no explicit when-to-use, when-not-to-use, or named alternative among the query_* siblings. For a fairly distinct dataset the routing risk is low, so this is adequate but incomplete.

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

All Energetica — Argentine Oil & Gas Data 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.

Resources

Need Help?