Skip to main content
Glama

Fuel price history

get_price_history
Read-onlyIdempotent

Read a bounded page of verified historical official fuel prices. Follow nextCursor until isDone; gaps mean missing evidence, not unchanged prices.

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": {
      "region": "<region>",
      "context": "<context>"
    },
    "name": "get_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuelNoExact regulated fuel category. Specialist fuels are not interchangeable with road diesel.
yearNo
limitNo
cursorNo
regionYesRegion whose official maximum prices to read.
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as \"a customer\". Do not quote the user or include names, emails, or other personal details.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The model identifier you are running as, for example \"claude-opus-4-8\" or \"gpt-5.2\". Pass \"unknown\" if you are not certain. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "region"
      -]New value: +[
      +  "region",
      +  "context"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the lower bar applies. The description adds genuinely useful behavior: results are 'verified' and 'official', the read is paged, and critically that gaps indicate missing evidence rather than unchanged prices — a data-interpretation caveat an agent could not derive from annotations.

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?

Two sentences, zero filler, and the core purpose plus pagination rule are front-loaded. The gap caveat is placed after the operational instruction where it is still prominent.

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

Completeness3/5

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

With no output schema, referencing 'nextCursor' and 'isDone' leaves those field names unexplained and slightly at odds with the parameter actually named 'cursor'. The description also omits the default page size, whether year is optional, and the price format or currency, which an agent would want before calling.

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 coverage is 57%, so the schema documents fuel, region, context and llm_model while year, limit and cursor are undocumented. The description only adds cursor-loop semantics, which is helpful but does not compensate for the silent year and limit parameters. A 3 baseline is fair.

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 a specific verb and resource: 'Read a bounded page of verified historical official fuel prices.' The 'historical' qualifier and 'bounded page' scope implicitly separate it from a current-prices sibling, but no sibling is named, so differentiation is left to inference.

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?

Gives pagination guidance ('Follow nextCursor until isDone') which tells the agent how to consume the tool across pages. However, it never says when to choose this over get_fuel_prices or find_fuel_articles, nor when history is inappropriate.

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.

Resources