Skip to main content
Glama

gpueuro: EU GPU cloud prices

EU price history for a GPU

price_history
Read-onlyIdempotent

Daily EU price history for a GPU model (cheapest, median, number of offers and price per provider for each day we have a check).

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": {
      "gpu": "<gpu>"
    },
    "name": "price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpuYes
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing what is returned per day and hinting at data availability gaps ('each day we have a check'). It says nothing about retention limits, latency or response size, so it goes only slightly beyond the annotations.

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?

A single front-loaded sentence with no filler; the parenthetical compactly lists the return fields. It is dense but readable, with no redundant restatement of the name or title.

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, the description usefully enumerates the return metrics, which is the right thing to cover. However, for a two-parameter tool with zero schema coverage it leaves both parameters undefined and offers no routing guidance against siblings, so it is only minimally complete.

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

Parameters2/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 the burden, and it does not. It never explains the expected format of 'gpu' (model name vs. identifier) nor mentions the 'days' window at all, despite that parameter having a default of 30 and a max of 365 that materially changes the result.

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 names a specific resource and scope: daily EU price history for a GPU model, and it enumerates the returned metrics (cheapest, median, offer count, per-provider price). It is clearly distinguishable from a live-price tool, but it does not explicitly contrast itself with siblings like cheapest_gpu or compare_providers.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. An agent must infer that this tool is for historical trends rather than current pricing, and nothing tells it whether to pair this with cheapest_gpu or compare_providers. Usage is only implied by the word 'history'.

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