Energetica — Argentine Oil & Gas Data

Wells search

query_wells

Read-onlyIdempotent

Wells in the registry (~86,000): location, type, current status and operator, cumulative production, first and last month with production, IP30. Example: {provincia: 'Neuquén', subtipo_recurso: 'SHALE', tipo_estado: 'activos'}.

Input Schema

Name	Required	Description
`orden`	No
`cuenca`	No
`empresa`	No
`max_rows`	No
`formacion`	No
`provincia`	No
`tipo_pozo`	No	e.g. Petrolífero, Gasífero
`yacimiento`	No
`tipo_estado`	No	Exact registry status (e.g. Abandonado, Parado Transitoriamente) or 'activos'
`segun_padron`	No
`tipo_recurso`	No
`area_concesion`	No
`con_produccion`	No
`subtipo_recurso`	No
`primera_produccion_desde`	No	First month with oil or gas > 0 (or the registry fecha_primera_prod with segun_padron)
`primera_produccion_hasta`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedOct 19, 2026

addedInput schema / properties / area_concesion
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / properties / con_produccion / description
```
Removed value: -"Only wells with cumulative production > 0"
```

removedInput schema / properties / cuenca / description

Removed value: -"Basin, partial match (NEUQUINA, GOLFO SAN JORGE, etc.)"

removedInput schema / properties / empresa / description
```
Removed value: -"Operating company, partial match"
```
removedInput schema / properties / formacion / description
```
Removed value: -"Geological formation, partial match"
```

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

Added value: +{
+  "enum": [
+    "acumulado",
+    "ip30",
+    "primera_produccion"
+  ],
+  "type": "string"
+}

addedInput schema / properties / primera_produccion_desde

Added value: +{
+  "description": "First month with oil or gas > 0 (or the registry fecha_primera_prod with segun_padron)",
+  "type": "string"
+}

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

removedInput schema / properties / provincia / description

Removed value: -"Province, partial match ignoring case and accents (e.g. Neuquén, Chubut, Santa Cruz)"

addedInput schema / properties / segun_padron
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / subtipo_recurso

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

changedInput schema / properties / tipo_estado / description

Previous value: -"Exact well status, or 'activos' for all active states (Extracción Efectiva, En Inyección Efectiva, Otras Situación Activo)"New value: +"Exact registry status (e.g. Abandonado, Parado Transitoriamente) or 'activos'"

removedInput schema / properties / tipo_estado / enum

Removed value: -[
-  "Extracción Efectiva",
-  "Abandonado",
-  "En Estudio",
-  "En Reserva para Recup. Sec./Asist.",
-  "Parado Transitoriamente",
-  "En Inyección Efectiva",
-  "A Abandonar",
-  "En Espera de Reparación",
-  "Otras Situación Inactivo",
-  "Abandono Temporario",
-  "Parado Alta Relación Agua/Petróleo",
-  "En Reserva de Gas",
-  "Otras Situación Activo",
-  "Parado Alta Relación Gas/Petróleo",
-  "En Reparación",
-  "Mantenimiento de Presión",
-  "activos"
-]

addedInput schema / properties / tipo_pozo

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

removedInput schema / properties / tipo_recurso / description

Removed value: -"Resource type (NO CONVENCIONAL = shale/tight)"

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"
+}

Changed7 schema fields changedOct 19, 2026

changedInput schema / properties / cuenca / description

Previous value: -"Basin filter (NEUQUINA, GOLFO SAN JORGE, etc.)"New value: +"Basin, partial match (NEUQUINA, GOLFO SAN JORGE, etc.)"

changedInput schema / properties / empresa / description

Previous value: -"Operating company filter"New value: +"Operating company, partial match"

changedInput schema / properties / formacion / description

Previous value: -"Geological formation"New value: +"Geological formation, partial match"

removedInput schema / properties / limit

Removed value: -{
-  "description": "Max results, default 100",
-  "maximum": 1000,
-  "minimum": 1,
-  "type": "number"
-}

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"
+}

changedInput schema / properties / provincia / description

Previous value: -"Province filter, partial match ignoring case and accents (e.g. Neuquén, Chubut, Santa Cruz)"New value: +"Province, partial match ignoring case and accents (e.g. Neuquén, Chubut, Santa Cruz)"

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"
+}

Changed1 schema field changedOct 18, 2026

changedInput schema / properties / provincia / description

Previous value: -"Province filter (NEUQUEN, CHUBUT, MENDOZA, etc.)"New value: +"Province filter, partial match ignoring case and accents (e.g. Neuquén, Chubut, Santa Cruz)"

Changed4 schema fields changedOct 18, 2026

changedInput schema / properties / tipo_estado / description

Previous value: -"Well status (e.g. Activo, Inactivo, Abandonado)"New value: +"Exact well status, or 'activos' for all active states (Extracción Efectiva, En Inyección Efectiva, Otras Situación Activo)"

addedInput schema / properties / tipo_estado / enum

Added value: +[
+  "Extracción Efectiva",
+  "Abandonado",
+  "En Estudio",
+  "En Reserva para Recup. Sec./Asist.",
+  "Parado Transitoriamente",
+  "En Inyección Efectiva",
+  "A Abandonar",
+  "En Espera de Reparación",
+  "Otras Situación Inactivo",
+  "Abandono Temporario",
+  "Parado Alta Relación Agua/Petróleo",
+  "En Reserva de Gas",
+  "Otras Situación Activo",
+  "Parado Alta Relación Gas/Petróleo",
+  "En Reparación",
+  "Mantenimiento de Presión",
+  "activos"
+]

changedInput schema / properties / tipo_recurso / description

Previous value: -"Resource type"New value: +"Resource type (NO CONVENCIONAL = shale/tight)"

changedInput schema / properties / tipo_recurso / enum

Previous value: -[
-  "PETROLEO",
-  "GAS",
-  "AMBOS"
-]New value: +[
+  "CONVENCIONAL",
+  "NO CONVENCIONAL",
+  "SIN RESERVORIO",
+  "NO DISCRIMINADO"
+]

First observedApr 29, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so safety is covered. The description usefully adds dataset scale (~86,000 wells) and the exact output fields, which informs the agent about result shape. It is silent on pagination, the max_rows default, or ordering behavior, so it adds moderate but not rich context.

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 sentences: the first front-loads the resource and output fields, the second provides a concrete filter example. No filler, no repetition of the title, and the most decision-relevant information leads.

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 not be described, and the description correctly focuses on scope and fields. However, for a 16-parameter, zero-required, 19%-documented search tool, the description does not explain how filters combine, the meaning of orden, or the default page size, leaving real gaps for correct invocation.

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?

Schema description coverage is only 19% across 16 parameters, so the description carries a heavy compensation burden. The example illustrates only three filters (provincia, subtipo_recurso, tipo_estado) and hints at the 'activos' shorthand, leaving cuenca, empresa, formacion, orden, max_rows, con_produccion and the date bounds unexplained. It adds marginal value over the schema without closing the coverage gap.

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 resource (wells in the registry), its scale (~86,000), and enumerates the returned fields: location, type, status, operator, cumulative production, first/last production month, IP30. This clearly distinguishes it from single-record siblings like get_well. It does not explicitly name why it differs from query_production or rank_entities, so it falls short of a 5.

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?

There is no explicit when-to-use/when-not statement and no reference to alternatives such as get_well or query_production. The example query object implies intended usage (filtering by provincia, subtipo_recurso, tipo_estado) but leaves the agent to infer routing. Implied usage only.

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?