Skip to main content
Glama

Swap options

list_swap_options
Read-onlyIdempotent

Lists available swap sizes for rebuilding a GoMami cloud server, enabling you to select a swap configuration before starting the rebuild.

Instructions

List the swap sizes available for a rebuild.

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": {
      "serverId": "<serverId>"
    },
    "name": "list_swap_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYesServer ID (UUID) from list_servers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered without the description. The description adds that results are scoped to a rebuild scenario, which is real context, but says nothing about whether the returned sizes depend on the server's current configuration or plan.

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 front-loaded sentence with no filler or repetition. It is efficient, though the brevity leaves room for a short clause on what a swap size represents without becoming bloated.

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?

This is a simple one-parameter read tool with no output schema and full annotation coverage, so little explanation is strictly required. Still, an agent gets no sense of what the returned sizes look like or how they should be applied during a rebuild, which is the tool's stated purpose.

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 description coverage is 100%, and serverId is documented in the schema as a UUID from list_servers, so the baseline of 3 applies. The description adds no further meaning about how serverId influences the returned swap options.

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 gives a clear verb ('List') and a specific resource ('swap sizes available for a rebuild'), which is distinguishable from siblings like list_isos or list_os_templates. It stops short of naming how it relates to the get_server/list_servers flow, and 'swap sizes' is slightly ambiguous (sizes of what unit), but the operation is identifiable.

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?

The phrase 'for a rebuild' hints at a workflow context but never states when an agent should call this versus inspecting server details directly, nor any prerequisite such as needing a valid serverId from list_servers. No alternatives or exclusions are mentioned, leaving usage entirely implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.