Skip to main content
Glama

Jodi Oil Compare

jodi_oil_compare
Read-onlyIdempotent

Compare JODI-Oil countries on one series, at the latest reported month AND against N months earlier, ranked by change. This is the tool for "which Gulf producers raised crude output most this quarter" (pass months_back:3) and "Saudi crude exports vs a year ago" (pass countries:["Saudi Arabia"], months_back:12), both are the same comparison, just different country lists. Defaults to the Gulf/Persian-Gulf producers (Saudi Arabia, UAE, Kuwait, Qatar, Oman, Bahrain, Iraq, Iran) 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_oil_compare({flow:"production", months_back:3}); jodi_oil_compare({countries:["Saudi Arabia"], flow:"exports", 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": "production",
      "months_back": 3
    },
    "name": "jodi_oil_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowNoproduction (default), imports, exports, closing_stocks, stock_change, etc, see jodi_oil_series
productNocrude (default), ngl, other, total, or a refined product, see jodi_oil_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. Changed2 schema fields changed
    • changedInput schema / properties / flow / description
      Previous value: -"production (default), imports, exports, closing_stocks, stock_change, etc — see jodi_oil_series"New value: +"production (default), imports, exports, closing_stocks, stock_change, etc, see jodi_oil_series"
    • changedInput schema / properties / product / description
      Previous value: -"crude (default), ngl, other, total, or a refined product — see jodi_oil_series"New value: +"crude (default), ngl, other, total, or a refined product, see jodi_oil_series"
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely useful behavior beyond them: the default Gulf country set, the treatment of missing months (reported:false, excluded from ranking rather than zero-filled), and keyless access. It still says nothing about output shape or value ordering.

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?

Purpose, example queries and default-set behavior are front-loaded, and every sentence carries information an agent needs. Minor waste in the aside "both are the same comparison, just different country lists" and the worked example calls that partly duplicate the schema examples.

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?

With five optional parameters, no required fields and no output schema, the description covers defaults, edge-case handling and invocation examples well. It stops short of describing the returned ranking fields (latest value, prior value, computed change), which an agent must infer for a comparison 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 description coverage is 100%, so every parameter is already documented, including the months_back 12=YoY/3=QoQ convention and the Gulf default. The description largely restates those semantics; its only real addition is spelling out the eight default country names explicitly. Baseline 3 applies.

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 and resource — comparing JODI-Oil countries on one series at the latest month versus N months earlier, ranked by change — which no sibling name captures. It also names jodi_oil_series as the place to discover flow/product values, so an agent can separate the two tools without opening a schema.

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?

Maps two concrete user questions ("which Gulf producers raised crude output this quarter", "Saudi crude exports vs a year ago") to exact parameter settings, which is strong routing guidance. It lacks an explicit when-not-to-use statement or a stated alternative for non-comparison queries, keeping it below a 5.

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.