Skip to main content
Glama

gpueuro: EU GPU cloud prices

Cheapest EU price for a GPU

cheapest_gpu
Read-onlyIdempotent

Cheapest on-demand price for a GPU model at EU cloud providers (EUR per GPU-hour, ex-VAT, checked daily). Optional filters: EU-owned providers only, data-centre country, how many GPUs you need (drops offers sold only in bigger bundles), no US parent, EU data centre.

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": "cheapest_gpu"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpuYesGPU model, e.g. H100, H200, B200, A100, L40S, RTX PRO 6000
limitNo
countryNoData-centre country, ISO code or name (e.g. DE, France)
min_gpusNoGPUs you need; offers whose smallest size is larger are excluded
no_us_parentNo
eu_owned_onlyNoOnly providers whose HQ and controlling owner are in the EU
eu_data_centreNoOnly offers with an EU/EEA data centre

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent and closed-world, so the safety profile is covered. The description adds genuinely new context: currency, tax treatment and daily refresh cadence, plus the bundle-size effect of min_gpus. It stops short of noting what happens when no offer matches.

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?

Purpose is front-loaded in one dense sentence, followed by a compact filter list. The trailing list partially duplicates the schema, but the total length is small and scannable.

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 seven parameters and no output schema, the description should say more about the shape of the result (provider, region, price fields) and what is returned when nothing matches. Pricing unit and freshness are covered, but the answer format is left implicit.

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 71%, so most parameters are already documented. The description adds real meaning for min_gpus (offers sold only in larger bundles are dropped), but the remaining filters are restated rather than explained, and 'no US parent' adds nothing over the parameter name.

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 resource and unit precisely: cheapest on-demand GPU price at EU cloud providers in EUR per GPU-hour, ex-VAT, refreshed daily. An agent can tell it is a pricing-lookup, not a history or comparison tool. It does not explicitly name a sibling to differentiate against, so it falls short of a 5.

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?

Usage is only implied by listing the optional filters; there is no statement of when to prefer this over price_history or compare_providers, nor any prerequisite or failure context. An agent can infer 'use for a single cheapest quote', but must guess the boundary cases.

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