Skip to main content
Glama

Jodi Gas Compare

jodi_gas_compare
Read-onlyIdempotent

Compare JODI-Gas countries on one series, at the latest reported month AND against N months earlier, ranked by change. Answers "which Gulf gas producers grew LNG exports most this year", "Qatar gas production vs last year". Defaults to the Gulf/Persian-Gulf producers if no countries are given. A country missing a compared month is marked reported:false and excluded from the ranking rather than treated as a zero. Example: jodi_gas_compare({flow:"exports_lng", months_back:12}). 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_back": 12
    },
    "name": "jodi_gas_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowNoproduction (default), imports, imports_lng, exports, exports_lng, closing_stocks, demand, etc, see jodi_gas_series
countriesNoISO2 codes or names; defaults to the Gulf producer set
end_monthNoLatest month to compare from, as YYYY-MM; defaults to the newest month anyone in the list has reported
months_backNoHow many months before the latest to compare against (default 12 = year-over-year; use 3 for quarter-over-quarter)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / flow / description
      Previous value: -"production (default), imports, imports_lng, exports, exports_lng, closing_stocks, demand, etc — see jodi_gas_series"New value: +"production (default), imports, imports_lng, exports, exports_lng, closing_stocks, demand, etc, see jodi_gas_series"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the description earns credit for adding real semantics: missing months are marked reported:false and excluded from the ranking rather than zero-filled, defaults for end_month, and 'Keyless' auth status. It does not describe the returned payload structure, which matters given there is no output schema.

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?

Front-loaded with the core behavior and scope, then defaults and edge-case handling; every sentence carries information except the trailing example, which repeats the schema's examples field. Dense but readable.

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 selection, defaults, ranking semantics, and missing-data behavior for a 4-parameter, zero-required tool. With no output schema, it should sketch the returned fields (country, values, change, reported) more concretely, which is the main residual gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds meaning by framing months_back as the lag in a change ranking (year-over-year vs quarter-over-quarter) and by noting countries default to the Gulf producer set. The inline example largely duplicates the schema's own examples entry, so the gain is modest rather than decisive.

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 (compare) plus the resource (JODI-Gas countries on one series) and pins down the comparison axis: latest reported month versus N months earlier, ranked by change. It also implicitly separates itself from jodi_gas_series, which the flow parameter description points to for series discovery.

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?

Gives concrete motivating questions ('which Gulf gas producers grew LNG exports most this year') and the default behavior when countries are omitted (Gulf/Persian-Gulf producer set). It does not explicitly state when NOT to use it (e.g. single-country time series → jodi_gas_series), so it stops short of full routing guidance.

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.