Skip to main content
Glama

List machines

list_vms
Read-only

The account's machines with their status, addresses and billing. Scope: vms.read.

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_vms"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMachines per page. Default 50.
cursorNonext_cursor from the previous page.
regionNoKeep only machines in this region (slug from list_regions).
statusNoe.g. running, stopped, provisioning.
billingNoKeep only machines billed this way.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / billing / description
      Added value: +"Keep only machines billed this way."
    • addedInput schema / properties / limit / description
      Added value: +"Machines per page. Default 50."
    • addedInput schema / properties / region / description
      Added value: +"Keep only machines in this region (slug from list_regions)."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds the required permission scope (vms.read), which the agent cannot infer from annotations, but says nothing about result ordering, page size defaults, or what happens when filters match nothing.

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?

Two short sentences, front-loaded with the resource and followed by the permission scope. Nothing is wasted, though the sentence fragment style leaves the scope clause slightly unanchored.

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

Completeness4/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 payload fields (status, addresses, billing) and the required scope, which is enough for a simple paginated list tool. Pagination behavior is left entirely to the schema, which is acceptable given full parameter 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%, so all five parameters are already documented in the schema. The description only implies the existence of status and billing filters by naming returned fields, adding no filter syntax or semantics beyond the schema; baseline 3 is appropriate.

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?

States a specific verb-and-resource: lists the account's machines, and names the fields returned (status, addresses, billing). It does not distinguish itself from nearby siblings such as list_vm_actions, but a list-of-VMs tool is clearly identifiable from the text alone.

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 or when-not-to-use guidance, and no pointer to alternatives such as list_vm_actions for machine-scoped operations. The only scoping hint is the permission string, which is an authorization fact rather than usage guidance.

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.