Energetica — Argentine Oil & Gas Data

Upstream investments

query_investments

Read-onlyIdempotent

Upstream oil & gas investments in Argentina by company, basin, year and concept, in millions of USD (drilling, workovers, pipelines, facilities, seismic…). Example: {cuenca: 'NEUQUINA', anio_desde: 2023, concepto: 'perforacion'}.

Input Schema

Name	Required	Description
`cuenca`	No
`empresa`	No
`concepto`	No	Investment concept, partial match ignoring accents (e.g. 'perforacion', 'reparacion de pozos', 'gasoductos', 'sismica')
`max_rows`	No
`anio_desde`	No	Year of the sworn statement (DDJJ)
`anio_hasta`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedOct 19, 2026

changedInput schema / properties / anio_desde / description

Previous value: -"Start year"New value: +"Year of the sworn statement (DDJJ)"

removedInput schema / properties / anio_desde / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / anio_desde / minimum
```
Removed value: --9007199254740991
```
changedInput schema / properties / anio_desde / type
```
Previous value: -"integer"New value: +"number"
```
removedInput schema / properties / anio_hasta / description
```
Removed value: -"End year"
```
removedInput schema / properties / anio_hasta / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / anio_hasta / minimum
```
Removed value: --9007199254740991
```
changedInput schema / properties / anio_hasta / type
```
Previous value: -"integer"New value: +"number"
```
removedInput schema / properties / cuenca / description
```
Removed value: -"Basin, partial match"
```
removedInput schema / properties / empresa / description
```
Removed value: -"Company, 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"

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

Changed11 schema fields changedOct 19, 2026

addedInput schema / properties / anio_desde / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / anio_desde / minimum
```
Added value: +-9007199254740991
```
changedInput schema / properties / anio_desde / type
```
Previous value: -"number"New value: +"integer"
```
addedInput schema / properties / anio_hasta / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / anio_hasta / minimum
```
Added value: +-9007199254740991
```
changedInput schema / properties / anio_hasta / type
```
Previous value: -"number"New value: +"integer"
```

changedInput schema / properties / concepto / description

Previous value: -"Investment concept, partial match (e.g. 'perforacion', 'reparacion de pozos', 'gasoductos', 'sismica')"New value: +"Investment concept, partial match ignoring accents (e.g. 'perforacion', 'reparacion de pozos', 'gasoductos', 'sismica')"

changedInput schema / properties / cuenca / description

Previous value: -"Basin filter"New value: +"Basin, partial match"

changedInput schema / properties / empresa / description

Previous value: -"Company filter"New value: +"Company, partial match"

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

Changed1 schema field changedOct 18, 2026

changedInput schema / properties / concepto / description

Previous value: -"Investment concept (e.g. perforacion, terminacion, infraestructura)"New value: +"Investment concept, partial match (e.g. 'perforacion', 'reparacion de pozos', 'gasoductos', 'sismica')"

First observedApr 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety is covered; the description adds materially useful context beyond that — output units in millions of USD and the concept taxonomy (drilling, workovers, pipelines, facilities, seismic). It says nothing about result size limits or pagination, so it stops 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?

Two tight sentences: the data scope and units come first, then filter dimensions, then a compact example. No filler, though the ellipsis list of concepts is mildly loose.

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?

An output schema exists, so return values need no explanation, and the description covers what the data is, its units and a working call example. The remaining gap is guidance on filter combinations and result limits, which is minor for a read-only filtered query.

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 only 33%, and only concepto and anio_desde carry descriptions. The description compensates partially by mapping the Spanish parameter names to dimensions (cuenca=basin, empresa=company, concepto=concept, anio_desde/year) and by demonstrating them in the example, but max_rows and anio_hasta remain 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 the specific resource (upstream oil & gas investments in Argentina), the breakdown dimensions (company, basin, year, concept) and the unit (millions of USD), which separates it from siblings like query_production, query_prices and query_reserves. It lacks an explicit verb ('query') and never names a sibling, so it is clear but not fully differentiated.

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 worked example shows a typical invocation with cuenca/anio_desde/concepto, which hints at filtered lookups, but there is no statement of when to prefer this over execute_sql, rank_entities or the other query_* tools, and no note that all filters are optional.

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?