Energetica — Argentine Oil & Gas Data

Read-only SQL

execute_sql

Read-onlyIdempotent

Run read-only DuckDB SQL (a single SELECT or WITH) over the catalog tables and views. Prefer the curated tools when they fit; call describe_data first for tables and columns. Column names and values are in Spanish. Example: {sql: "SELECT anio, SUM(prod_petroleo_m3) FROM agg_produccion_mensual WHERE formacion = 'vaca muerta' GROUP BY 1 ORDER BY 1"}.

Input Schema

Name	Required	Description	Default
`sql`	Yes
`max_rows`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 19, 2026

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"

removedInput schema / properties / sql / description

Removed value: -"SQL query (a single SELECT or WITH)"

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

Changed4 schema fields changedOct 19, 2026

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 / sql / description

Previous value: -"SQL query (SELECT or WITH only)"New value: +"SQL query (a single SELECT or WITH)"

addedInput schema / properties / sql / minLength
```
Added value: +1
```

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

First observedApr 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the bar is lower, yet the description still adds real context: only a single statement is accepted, and column names/values are in Spanish, which is a non-obvious behavioral gotcha. It does not mention row-limiting behavior or query cost, so it falls 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core capability and followed by routing guidance, prerequisite, a caveat, and a worked example. The example is long but directly earns its place by showing dialect, table naming, and aggregation style.

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 scope, safety, language gotcha, and prerequisite. The only gap is the undocumented 'max_rows' parameter and the default row cap, which matters for an agent composing open-ended SQL.

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 0%, so the description must carry the burden. It compensates well for the 'sql' parameter with the single-statement rule, the Spanish naming caveat, and a concrete example query, but 'max_rows' is never mentioned anywhere, leaving one of two parameters entirely undocumented.

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 (Run), resource (DuckDB SQL over catalog tables and views), and constraint (read-only, a single SELECT or WITH). This clearly distinguishes it from the curated siblings like query_production and get_well, which the description explicitly positions as preferred alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when not to use it ('Prefer the curated tools when they fit') and names a required prerequisite workflow ('call describe_data first for tables and columns'). Both the alternative and the ordering constraint are stated, leaving nothing to inference.

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?