Skip to main content
Glama

list_fleets

Read-onlyIdempotent

List machine fleets with their action or workspace mode and guarded status; omit context to review every configured context and see any context errors.

Instructions

List fleets (groups of machines) with their mode (actions or workspace) and whether each is guarded. With no context it lists every configured context; a context that fails is reported in errors[]. Guarded fleets need the user's explicit agreement before any state-changing call.

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

Input Schema

NameRequiredDescriptionDefault
contextNoContext name. Omit to list every context.

Output Schema

NameRequiredDescriptionDefault
errorsYes
fleetsYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds useful behavior beyond that: partial-failure reporting via errors[] and the guarded-fleet consent requirement. It does not describe pagination or result ordering, so it is solid but not rich.

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?

Three tight sentences, front-loaded with the core purpose, then scoping behavior, then the guarded-fleet caveat. No redundant or filler wording.

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?

An output schema exists, so return values need not be explained, and the description still names the salient fields (mode, guarded, errors[]). For a read-only single-parameter list tool this is nearly complete; only pagination/ordering details are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single context parameter is already documented, so the baseline is 3. The description adds meaning by spelling out the consequence of omitting context (lists every configured context), which goes slightly beyond the schema's 'Omit to list every context.'

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 ('List fleets') and immediately clarifies what a fleet is ('groups of machines') plus what is returned (mode and guarded status). It does not explicitly name a sibling to distinguish from, but the resource is distinct enough that an agent can identify it.

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?

Explains the key usage decision: omitting context lists every configured context, and per-context failures surface in errors[]. It also flags that guarded fleets require explicit user agreement before state-changing calls, which is actionable context, though it does not contrast with any alternative tool.

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