Skip to main content
Glama

Jodi Gas Series

jodi_gas_series
Read-onlyIdempotent

Monthly JODI-Gas series for one country, production, imports/exports (total, or LNG vs pipeline split out), demand, stock change or closing stocks, natural gas only. Answers "Qatar LNG exports over the last 3 years", "Iran gas production trend", "UAE gas imports by pipeline vs LNG". A month with no JODI submission comes back as {reported:false, value:null}, NEVER 0. Example: jodi_gas_series({country:"Qatar", flow:"exports_lng", months:36}). Keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "flow": "exports_lng",
      "months": 36,
      "country": "Qatar"
    },
    "name": "jodi_gas_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowNoproduction (default), imports, imports_lng, imports_pipeline, exports, exports_lng, exports_pipeline, closing_stocks, stock_change, demand, demand_calculated, electricity_generation, statistical_difference, other_sources
monthsNoHow many trailing months (default 24, max 120)
countryYesISO2 code ("QA") or name ("Qatar")
end_monthNoLast month of the window as YYYY-MM; defaults to the latest month JODI has published for anyone

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive. The description adds non-obvious behavior: a missing month returns {reported:false, value:null}, never 0, and it notes the endpoint is 'Keyless'. It does not cover update lag or rate limits, but the key semantic caveat is explicit.

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?

Front-loads purpose, flow coverage, example queries, the null-return rule and 'Keyless' in a compact block. Every sentence contributes useful selection or interpretation information, with no filler.

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?

Covers scope, missing-data semantics, example invocation and authentication context for a read-only series tool. It omits value units (e.g., mcm or TJ) and data update cadence, which would help interpret returned values, but the essential calling information is present.

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 100%, so all four parameters, including the flow list and defaults, are already documented. The description restates some flow options and gives an example call, but adds little syntactic or semantic detail beyond the schema; a baseline 3 is appropriate.

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 resource (Monthly JODI-Gas series for one country) and enumerates the flows it can return, including the LNG vs pipeline split. 'For one country' implicitly distinguishes it from jodi_gas_compare, and 'natural gas only' scopes it against oil siblings.

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

Usage Guidelines4/5

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

Provides example natural-language queries and an example call, giving clear context for typical usage. It does not explicitly say when not to use it or point to jodi_gas_compare for multi-country comparisons, so it falls short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.