Skip to main content
Glama
Sign In

OilPriceAPI hosted energy data

by io.github.OilpriceAPI
OverviewDiscussionsAdmin

Compare Energy Benchmarks

energy_compare
Read-onlyIdempotent

Compare 2–5 distinct supported energy benchmarks with separate timestamps, dataset context, units and currencies. No currency conversion or timestamp alignment is implied.

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": {
      "benchmarks": "<benchmarks>"
    },
    "name": "energy_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
benchmarksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds important semantics beyond that: results preserve separate timestamps, dataset context, units, and currencies, and no conversion or alignment is performed.

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?

Two concise sentences front-load the action and bounds with no filler. The metadata phrase is compact but slightly ambiguous about what is supplied versus returned.

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?

For a one-parameter read-only comparison tool with rich annotations and no output schema, the definition provides enough scope and normalization caveats. It could be more explicit about the return shape, but that is not essential here.

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?

There is only one parameter, and the schema defines it as an enum array with min/max bounds, but schema description coverage is 0%, so the description must add meaning. It adds the "distinct" constraint and mentions separate metadata, but does not explain the enum values or clarify whether timestamps and currencies are inputs or output context.

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?

States the specific verb "Compare" and the resource "energy benchmarks," and bounds the scope to 2–5 distinct supported benchmarks. It does not explicitly contrast with sibling tools such as energy_get_latest, but the comparison operation itself is clear.

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?

Explains the comparison context and limits, including that currency conversion and timestamp alignment are not implied. However, it does not say when to choose this tool over siblings or when not to use it, so usage is implied rather than explicit.

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