Skip to main content
Glama

List images

list_images
Read-only

Operating systems and ready-to-use application images. The slug is what create_vm expects. Public, no key needed.

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

Input Schema

NameRequiredDescriptionDefault
planNoKeep only images that fit this plan.
regionNoKeep only images offered in this region (slug from list_regions).
categoryNolinux, windows, bsd or app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / region / description
      Added value: +"Keep only images offered in this region (slug from list_regions)."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely useful context beyond them: the catalog is public and requires no API key. It stops short of covering pagination, result volume, or whether filtering happens server-side, which matters for an open-world listing.

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?

Three short sentences, front-loaded with what the resource is and followed by the two facts an agent actually needs (slug handoff, no auth). No filler, though it is terse enough to border on under-specification.

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 and three optional params, the description covers the essentials: what the records represent, the key field consumed downstream, and the auth posture. Ideally it would say more about the returned fields and how filters combine, but nothing critical is missing.

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%, with plan, region, and category each documented in the schema (including the 'slug from list_regions' pointer). The description adds no meaning about these filters, so the baseline 3 applies.

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 names the resource concretely (OS and ready-to-use application images) and links it to a sibling by stating 'The slug is what create_vm expects.' The listing verb is only implied through the name/title rather than stated, but the resource and its purpose are unambiguous.

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

Usage Guidelines3/5

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

There is an implied workflow hint: fetch images here so their slug can be fed to create_vm. However, it never states when to call this versus the other list_* tools (list_plans, list_regions) that also supply filters for this call, and offers no exclusions or prerequisites.

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.