Skip to main content
Glama

gpueuro: EU GPU cloud prices

Compare EU providers for a GPU

compare_providers
Read-onlyIdempotent

Every EU provider that lists a GPU model on demand, cheapest first, with country, minimum GPU count, sovereignty tags and source link.

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

Input Schema

NameRequiredDescriptionDefault
gpuYes
countryNo
eu_owned_onlyNo

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 genuine context beyond that: results are sorted cheapest first, restricted to EU on-demand listings, and include sovereignty tags plus a source link. It still says nothing about paging, result caps, or what happens when no provider 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?

A single dense sentence that front-loads scope and sort order with no filler. It is efficient, though the fragmentary style means the agent has to parse a list of output fields rather than read a clean purpose statement.

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 returned fields, which partly compensates. But for a tool with 0% schema coverage across three parameters, the absence of any parameter semantics or usage routing leaves an agent guessing how to construct a correct call.

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 parameter burden and does not. The required 'gpu' parameter's accepted format (exact model name? alias? case sensitivity?) is unstated, 'country' is ambiguous because it also appears as an output field rather than a filter, and 'eu_owned_only' is never mentioned at all.

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 states a precise scope: every EU provider listing a GPU model on demand, ordered cheapest first. That is specific enough to distinguish it from siblings like cheapest_gpu or list_providers, but it never explicitly names or contrasts with any of them, and it is phrased as a noun fragment rather than stating the comparison verb.

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 when-to-use guidance, no statement of when not to use it, and no reference to the alternatives (cheapest_gpu, price_history, request_quote_link). The phrase 'on demand' hints at a listing-type scope, but the agent must infer the selection conditions entirely from context.

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