Skip to main content
Glama
Sign In

OilPriceAPI hosted energy data

by io.github.OilpriceAPI
OverviewDiscussionsAdmin

Energy Price History

energy_history
Read-onlyIdempotent

Read one authenticated benchmark's daily historical observations over at most 30 days and 100 rows. No pagination or anonymous history. Derive summaries only from returned observations, which may be incomplete.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "benchmark": "<benchmark>",
      "days": "<days>",
      "limit": "<limit>"
    },
    "name": "energy_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
limitYes
benchmarkYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description usefully adds that authentication is required, that there is no pagination past the caps, and that observations may be incomplete — but it omits what happens on over-limit requests and the shape/normalization of the returned series. Some of the stated limits (30/100) merely repeat the schema maximums.

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?

Three short sentences with no filler; the scope constraint precedes the behavioral caveats. Every clause carries an actionable fact for the caller.

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 no output schema, the description does enough for a bounded read tool: it discloses authentication, row and day caps, absence of pagination, and the risk of incomplete data. The remaining gap is the time anchor for the window (ending when?) and the granularity of a 'row'.

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 0%, so the description must carry parameter meaning. It does map the parameters loosely ('one ... benchmark', 'at most 30 days', '100 rows'), but that largely restates the schema's maximums, and it never clarifies whether 'days' counts backward from today, nor what 'rows' represent per day.

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 uses a specific verb and resource ('Read ... daily historical observations') and pins the scope to 'one authenticated benchmark', which implicitly separates it from the comparison-style siblings. It does not name any sibling explicitly, so an agent must infer the split between history and latest/compare.

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

Usage Guidelines3/5

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

'No pagination or anonymous history' communicates hard constraints rather than when-to-use guidance, and the single-benchmark scope hints that comparison use cases belong elsewhere. There is no explicit routing statement such as 'use energy_get_latest for the current price' or 'use energy_compare for multiple benchmarks'.

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

All OilPriceAPI hosted energy 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