Skip to main content
Glama
OilpriceAPI

OilPriceAPI

Official
by OilpriceAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Get Marine Fuel Prices

opa_get_marine_fuels
Read-only

Retrieve current marine fuel (bunker) prices by port and fuel type, with currency, unit, and as-of time. Filter by port name or UN/LOCODE and fuel type.

Instructions

Get latest marine fuel (bunker) prices returned for the account, one row per port and fuel, each with the currency, unit, as-of time, age in days and stale flag the API reports. Use when the user asks about bunker fuel, marine fuel, VLSFO, MGO, IFO380, or shipping fuel costs. Filter by port name or UN/LOCODE (e.g., Singapore or SGSIN, Rotterdam or NLRTM) and/or by the fuel type the API reports: VLSFO, MGO_05S (MGO), HFO_380 (IFO380). Requires an eligible account entitlement. Use opa_get_plans for current access and pricing; the API response is authoritative.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portNoFilter by port name or UN/LOCODE, case-insensitive (e.g., 'Singapore' or 'SGSIN', 'Houston' or 'USHOU')
fuel_typeNoFilter by fuel type as the API reports it: VLSFO, MGO_05S (MGO also matches), HFO_380 (IFO380 also matches)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.4.1
    • changedInput schema / properties / fuel_type / description
      Previous value: -"Filter by fuel type: VLSFO, MGO, or IFO380"New value: +"Filter by fuel type as the API reports it: VLSFO, MGO_05S (MGO also matches), HFO_380 (IFO380 also matches)"
    • changedInput schema / properties / port / description
      Previous value: -"Filter by port name (e.g., 'SINGAPORE', 'ROTTERDAM', 'HOUSTON')"New value: +"Filter by port name or UN/LOCODE, case-insensitive (e.g., 'Singapore' or 'SGSIN', 'Houston' or 'USHOU')"
  2. Addedv3.2.0
  3. Removedv3.0.0
  4. First observedv2.0.0

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint and openWorldHint, and the description adds useful context: the response is account-specific, includes an as-of time, age in days, and a stale flag, and the API response is authoritative. This goes beyond the basic annotation hints without contradicting them.

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?

The description is dense but well-organized: it opens with what the tool returns, then when to use it, then how to filter and what constraints apply. Every sentence serves a purpose, and there is no redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by listing return contents, row granularity, filtering options, accepted aliases, and entitlement requirements. It covers what an agent needs to select and invoke the tool correctly, including an authoritative fallback for access questions.

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

Parameters5/5

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

Schema coverage is 100%, and the description further clarifies parameter usage with concrete examples like Singapore/SGSIN and Rotterdam/NLRTM, case-insensitive matching, and fuel type aliases (MGO_05S matches MGO, HFO_380 matches IFO380). This adds real meaning beyond the schema's property descriptions.

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?

The description clearly states the tool returns latest marine fuel (bunker) prices, one row per port and fuel, with specific fields like currency, unit, as-of time, age, and stale flag. This distinctly identifies the resource and output shape, setting it apart from siblings focused on diesel, natural gas hubs, or other commodities.

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?

The description explicitly says when to use it: when the user asks about bunker fuel, marine fuel, VLSFO, MGO, IFO380, or shipping fuel costs. It also points to opa_get_plans for access and pricing, giving an alternative for related but different needs.

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

Deploy Server

Other Tools