Skip to main content
Glama

gpueuro: EU GPU cloud prices

Link to request a quote

request_quote_link
Read-onlyIdempotent

Returns a pre-filled link to the gpueuro quote form for multi-GPU or reserved capacity from EU clouds that do not publish prices (e.g. STACKIT, Sesterce, evroc, Nscale). Only returns a URL for the user to open; nothing is submitted.

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>",
      "count": "<count>"
    },
    "name": "request_quote_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpuYes
countYes
countryNo
providerNoOptional: one quote-only provider name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and idempotentHint=true; the description adds the non-obvious guarantee that 'nothing is submitted' and that the output is purely a URL for the user to open, which prevents an agent from treating it as an outbound request. It stops short of saying whether the generated link expires or can be reused, which matters for an idempotent-hinted tool.

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, both earning their place: the first defines scope and output, the second closes the biggest ambiguity (no submission side effect). Front-loaded with the return value and zero filler.

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?

For a 4-parameter read-only tool with no output schema, the description covers what is returned and that it is side-effect free, which is the critical part. It is thin on parameter semantics and silent on link lifetime/reuse, leaving real gaps for an agent constructing the 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 only 25% (only 'provider' is documented), so the description is expected to compensate and largely does not. It supplies useful provider examples that map to the provider param, but adds no meaning for 'gpu' (expected name/format), 'count', or 'country' — an agent gets no guidance on accepted GPU naming or the units/semantics of count beyond the 1–99999 bounds.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb+resource ('Returns a pre-filled link to the gpueuro quote form') and scopes it precisely to multi-GPU/reserved capacity on EU clouds that do not publish prices, naming concrete examples (STACKIT, Sesterce, evroc, Nscale). An agent can tell this apart from the price-query siblings without opening any schema.

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

Usage Guidelines4/5

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

States the triggering condition clearly: use it for multi-GPU or reserved-capacity requests from providers without published prices. It does not explicitly name the sibling to use instead when prices ARE published (e.g. cheapest_gpu), so the exclusion is implied rather than spelled out.

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