Skip to main content
Glama
Sign In

Energetica — Argentine Oil & Gas Data

by ar.energetica
OverviewDiscussionsAdmin

Hydrocarbon trade balance

query_trade
Read-onlyIdempotent

Argentina hydrocarbon exports and imports by month: crude oil (HS 2709), refined products (HS 2710) and natural gas (HS 2711), FOB USD and kg. Example: {anio: 2025, flow: 'export', producto: 'crude'}.

Input Schema

NameRequiredDescriptionDefault
anioNo
flowNoTrade flow direction
max_rowsNo
productoNoProduct category

Output Schema

NameRequiredDescriptionDefault
metaYes
rowsYes
columnsYes
sectionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • removedInput schema / properties / anio / description
      Removed value: -"Filter by year"
    • removedInput schema / properties / anio / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / anio / minimum
      Removed value: --9007199254740991
    • changedInput schema / properties / anio / type
      Previous value: -"integer"New value: +"number"
    • 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"
+}
  2. Changed5 schema fields changed
    • addedInput schema / properties / anio / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / anio / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / anio / type
      Previous value: -"number"New value: +"integer"
    • 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"
+}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful domain context: geographic scope, monthly granularity, the HS-coded product taxonomy, and reporting units. It says nothing about pagination, defaults for optional params, or result limits, so it clears the lowered bar but does not exceed it.

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 sentences: the data scope is front-loaded, followed by a compact example. Every element earns its place, with no filler or restatement of the title.

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 annotations cover safety and determinism. However, with zero required parameters the description should clarify defaults (e.g., what happens if producto or flow is omitted, what max_rows defaults to), and it does not. Adequate but with a clear gap for an all-optional-parameter query tool.

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 coverage is 50% (flow and producto documented in-schema; anio and max_rows not). The description compensates partly by listing the product categories that map to the 'producto' enum and by giving a concrete example ({anio: 2025, flow: 'export', producto: 'crude'}) that demonstrates value shapes. It still leaves max_rows and the anio format undiscussed, so it adds only marginal meaning beyond the schema.

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 a specific resource (Argentina hydrocarbon exports/imports by month) and enumerates the exact products with HS codes (2709, 2710, 2711) and units (FOB USD, kg). This clearly distinguishes it as the trade-data query within the query_* family, though it never names a sibling tool to contrast against.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are mentioned. The example invocation shows the call syntax but does not tell the agent when to reach for this tool versus query_prices or query_production.

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 toolsInspect
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