Skip to main content
Glama

List UpCloud options

list_upcloud_options
Read-only

List the LIVE UpCloud catalogue a credential can reach: every datacentre zone with UpCloud's own description, and every server plan with its vCPU, memory, storage, current_offering flag, monthly EUR list price, and - for the GPU plans - gpu_count and gpu_model. ALWAYS call this instead of list_instance_types before create_upcloud_cluster or before answering any question about UpCloud zones, plans, GPUs, or prices: list_instance_types serves a frozen offline snapshot that stops at PREMIUM-8xCPU-32GB and contains NO GPU plan, so it cannot be used to conclude that UpCloud offers no GPU. UpCloud's two Helsinki zones are told apart only by their description, so read the zone list rather than guessing from the zone id. It also lists gateway_plans, the NAT gateway plans create_upcloud_cluster's gateway_plan accepts, with bandwidth_mbps, server_number and high_availability (a one-server plan loses all cluster egress while UpCloud rebuilds it). Read-only; talks to the UpCloud API, so it can take a few seconds.

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": {
      "credential_id": "<credential_id>"
    },
    "name": "list_upcloud_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneNoOptional zone id (e.g. 'fi-hel2') to price the plans for. Omit to price against the first zone UpCloud returns.
credential_idYesUUID of the UpCloud API credential. Call list_provider_credentials first and pass the credential's 'id' value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint=true, it discloses that the data is live, that it hits the UpCloud API and can take a few seconds, that the current_offering flag exists, and the operational consequence that a one-server gateway plan loses all cluster egress during a rebuild. It also flags a real failure mode (concluding 'no GPU' from the stale sibling).

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?

Front-loaded with the core purpose and the critical 'call this instead' rule, then supporting detail. It is dense and slightly run-on, with several clauses stacked into long sentences, but essentially no sentence is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by enumerating the returned fields (zones with descriptions, plan specs, prices, GPU fields, gateway plan bandwidth/server_number/high_availability). An agent can call this and interpret the result without further documentation.

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 100% and both parameters are documented there, including the credential_id lookup chain and the zone default behavior. The description only implies zone-based pricing implicitly; it adds no format or selection detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('List the LIVE UpCloud catalogue a credential can reach') and immediately enumerates scope: datacentre zones, server plans with vCPU/memory/storage/offering/price, GPU fields, and gateway plans. It is unambiguously distinguishable from list_instance_types and the other list_* options tools.

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

Usage Guidelines5/5

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

Gives explicit routing instructions: ALWAYS use this instead of list_instance_types before create_upcloud_cluster or when answering questions about zones, plans, GPUs, or prices, and explains why (the snapshot stops at PREMIUM-8xCPU-32GB and has no GPU plans). It also warns to read zone descriptions rather than infer from zone ids.

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.