Skip to main content
Glama

gpueuro: EU GPU cloud prices

List EU GPU cloud providers

list_providers
Read-onlyIdempotent

EU GPU cloud providers tracked by gpueuro with sovereignty facts: EU ownership, US parent, EU data centres, certifications, GPU models and whether they are quote-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
no_us_parentNo
certificationNoe.g. ISO27001, C5, SecNumCloud, SOC2, HDS
eu_owned_onlyNo
eu_data_centreNoOnly providers whose every priced offer is in an EU/EEA data centre
include_quote_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, covering the safety profile. Beyond that the description only notes that quote-only providers are part of the dataset, which is a data property rather than behavior; it adds nothing about result size, pagination, or what happens when all filters are omitted.

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 dense sentence with no filler, and the identifying scope ('EU GPU cloud providers tracked by gpueuro') is front-loaded. The colon-separated fact list is efficient, though slightly packed for one sentence.

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 sovereignty fields returned, which is the main completeness win. However, with five optional filters at 40% coverage and no annotations gaps remaining, it should also clarify filter semantics and whether the default returns quote-only providers as well as priced ones.

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 only 40% and only eu_data_centre carries a schema description, so the description is expected to compensate. It partially does by naming the underlying facts (EU ownership, US parent, EU data centres, certifications, quote-only), which map to no_us_parent, eu_owned_only, eu_data_centre, certification, and include_quote_only, but it never states the filter direction or interaction (e.g., how no_us_parent relates to eu_owned_only).

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 (EU GPU cloud providers tracked by gpueuro) and enumerates the sovereignty facts attached to each one, so an agent knows what comes back. It never uses an explicit verb like 'list' or 'filter', and it does not distinguish itself from siblings such as compare_providers or cheapest_gpu.

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 guidance on when to call this versus compare_providers, cheapest_gpu, or price_history, nor any statement of prerequisites or exclusions. The filters' boolean toggles are also left without usage rationale, so the agent must infer the selection scenario from the tool name alone.

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