Energetica — Argentine Oil & Gas Data

Monthly hydrocarbon production

query_production

Read-onlyIdempotent

Oil, gas and water production (2006–present) by entity and period, grouped by up to 3 dimensions: volumes, BOE, producing/reporting wells, daily rate, GOR, water cut. Example: {area_concesion: "LOMA CAMPANA", fecha_desde: "2025", agrupar_por: ["anio"]}.

Input Schema

Name	Required	Description
`cuenca`	No
`idpozo`	No
`empresa`	No
`max_rows`	No
`metricas`	No	Default petroleo, gas, agua (+ pozos_productores by mes); caudal_diario = volume / calendar days
`formacion`	No
`provincia`	No
`tipo_pozo`	No	e.g. Petrolífero, Gasífero
`yacimiento`	No
`agrupar_por`	No	Up to 3 dimensions; default [mes]
`fecha_desde`	No
`fecha_hasta`	No	Inclusive
`tipo_recurso`	No
`area_concesion`	No
`subtipo_recurso`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedOct 19, 2026

changedInput schema / properties / agrupar_por / description

Previous value: -"Group results by dimension. Default: mes"New value: +"Up to 3 dimensions; default [mes]"

removedInput schema / properties / agrupar_por / enum

Removed value: -[
-  "mes",
-  "anio",
-  "cuenca",
-  "empresa",
-  "formacion"
-]

addedInput schema / properties / agrupar_por / items

Added value: +{
+  "enum": [
+    "mes",
+    "anio",
+    "empresa",
+    "cuenca",
+    "provincia",
+    "area_concesion",
+    "yacimiento",
+    "formacion",
+    "tipo_recurso",
+    "subtipo_recurso",
+    "tipo_pozo",
+    "idpozo"
+  ],
+  "type": "string"
+}

addedInput schema / properties / agrupar_por / maxItems
```
Added value: +3
```
changedInput schema / properties / agrupar_por / type
```
Previous value: -"string"New value: +"array"
```
addedInput schema / properties / area_concesion
```
Added value: +{
+  "type": "string"
+}
```

removedInput schema / properties / cuenca / description

Removed value: -"Basin, partial match (e.g. NEUQUINA, GOLFO SAN JORGE, CUYANA, AUSTRAL, NOROESTE)"

removedInput schema / properties / empresa / description

Removed value: -"Operating company, partial match (e.g. YPF, PAN AMERICAN, VISTA, TECPETROL)"

removedInput schema / properties / fecha_desde / description

Removed value: -"Start period YYYY or YYYY-MM (e.g. 2020-01)"

changedInput schema / properties / fecha_hasta / description

Previous value: -"End period YYYY or YYYY-MM, inclusive (e.g. 2025-12)"New value: +"Inclusive"

removedInput schema / properties / formacion / description

Removed value: -"Geological formation, partial match (e.g. VACA MUERTA, D-129)"

addedInput schema / properties / idpozo

Added value: +{
+  "items": {
+    "type": "number"
+  },
+  "maxItems": 50,
+  "type": "array"
+}

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"

addedInput schema / properties / metricas

Added value: +{
+  "description": "Default petroleo, gas, agua (+ pozos_productores by mes); caudal_diario = volume / calendar days",
+  "items": {
+    "enum": [
+      "petroleo",
+      "gas",
+      "agua",
+      "boe",
+      "gor",
+      "water_cut",
+      "pozos_productores",
+      "pozos_informantes",
+      "caudal_diario"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / provincia
```
Added value: +{
+  "type": "string"
+}
```

removedInput schema / properties / recurso

Removed value: -{
-  "description": "Resource type filter. Default: todos",
-  "enum": [
-    "petroleo",
-    "gas",
-    "agua",
-    "todos"
-  ],
-  "type": "string"
-}

addedInput schema / properties / subtipo_recurso

Added value: +{
+  "enum": [
+    "SHALE",
+    "TIGHT"
+  ],
+  "type": "string"
+}

addedInput schema / properties / tipo_pozo

Added value: +{
+  "description": "e.g. Petrolífero, Gasífero",
+  "type": "string"
+}

addedInput schema / properties / tipo_recurso

Added value: +{
+  "enum": [
+    "CONVENCIONAL",
+    "NO CONVENCIONAL",
+    "SIN RESERVORIO",
+    "NO DISCRIMINADO"
+  ],
+  "type": "string"
+}

addedInput schema / properties / yacimiento
```
Added value: +{
+  "type": "string"
+}
```
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"
+}

Changed5 schema fields changedOct 19, 2026

changedInput schema / properties / cuenca / description

Previous value: -"Basin name filter (e.g. NEUQUINA, GOLFO SAN JORGE, CUYANA, AUSTRAL, NOROESTE)"New value: +"Basin, partial match (e.g. NEUQUINA, GOLFO SAN JORGE, CUYANA, AUSTRAL, NOROESTE)"

changedInput schema / properties / empresa / description

Previous value: -"Operating company filter (e.g. YPF, PAN AMERICAN ENERGY, VISTA, TECPETROL)"New value: +"Operating company, partial match (e.g. YPF, PAN AMERICAN, VISTA, TECPETROL)"

changedInput schema / properties / formacion / description

Previous value: -"Geological formation filter (e.g. VACA MUERTA, D-129, CENTENARIO)"New value: +"Geological formation, partial match (e.g. VACA MUERTA, D-129)"

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

changedInput schema / properties / fecha_desde / description

Previous value: -"Start date YYYY-MM (e.g. 2020-01)"New value: +"Start period YYYY or YYYY-MM (e.g. 2020-01)"

changedInput schema / properties / fecha_hasta / description

Previous value: -"End date YYYY-MM (e.g. 2025-12)"New value: +"End period YYYY or YYYY-MM, inclusive (e.g. 2025-12)"

First observedApr 29, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: the 2006–present coverage window, the set of computable metrics, and the hard constraint of at most 3 grouping dimensions. It still omits operational behavior such as row limits or rate limits.

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 tightly packed sentences: scope and metrics first, then an inline example. No filler, and the most decision-relevant information is front-loaded.

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

Completeness3/5

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

An output schema exists, so return values need no explanation. However, for a 15-parameter, zero-required query tool with sparse schema descriptions, the definition does not explain how the many filter parameters interact, what the defaults are, or when to use this versus the other query tools.

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

Parameters2/5

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

With 15 parameters and only 27% schema description coverage, the description carries most of the burden but does not deliver. It restates metricas and agrupar_por (which the schema already documents) while leaving cuenca, idpozo, empresa, max_rows, formacion, provincia, yacimiento, fecha_hasta, tipo_recurso and subtipo_recurso unexplained in both places.

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+resource — querying oil, gas and water production by entity and period — with the data window (2006–present) and grouping capability. An agent can tell it is a production-data query, but it never distinguishes itself from sibling query_* tools such as query_wells or query_completions.

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: the example payload shows one way to call it, but there is no statement of when to prefer this over execute_sql, describe_data, or the other query_* siblings, and no exclusions or prerequisites.

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?