Skip to main content
Glama

Control Plane

by io.cpln

List Commands

list_commands
Read-onlyIdempotent

List the asynchronous operation commands issued against a workload or volumeset — cron runs and replica stops (workload), or volume expand / shrink / snapshot / restore / delete (volumeset). Each row shows the command id, type, lifecycleStage (pending → running → completed / failed), and message count. Pass kind (workload|volumeset), gvc, and name; optionally filter by lifecycleStage. Use get_command for one command’s full status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gvcYesGVC slug (lowercase kebab-case). Use the GVC the user named; otherwise discover with list_resources (kind="gvc") and let them choose — never guess (a wrong GVC targets the wrong environment).
orgYesOrganization slug (lowercase kebab-case). NEVER guess — if the user has not named one, ask. On org-not-found, stop and ask; do not retry variants.
kindYesParent resource that owns the command — `workload` (cron runs via workload_start_cron, replica stops via workload_stop_replica) or `volumeset` (volume expand / shrink / snapshot / restore / delete). Both are GVC-scoped.
nameYesName of the parent workload or volumeset whose commands to list.
limitNoMaximum number of items to return (1-500, default: all).
lifecycleStageNoOptional server-side filter — return only commands in this lifecycle stage (terminal: completed, failed, cancelled).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the call succeeded.
dataNoThe full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary.
summaryYesOne-line summary of the result.
nextStepsNoRecommended follow-up actions for this task, in order.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by explaining lifecycleStage transitions (pending → running → completed/failed) and the kinds of operations (cron runs, replica stops, volume operations), which goes beyond the annotations without contradicting them.

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?

The description is two sentences: first explains what is listed and shown; second explains required/optional parameters and points to get_command. It packs substantial detail without redundancy or filler.

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?

The tool has a rich output schema and annotations, so the description doesn't need to explain return structure. It fully covers scope, required inputs, and alternative tools. The only minor gap is not specifying a default for limit (schema says 'default: all'), but that is present in the schema.

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 detailed descriptions for all six parameters (e.g., 'kind' explains workload vs. volumeset; 'gvc' includes discovery guidance). The tool description adds minimal parameter-level semantics beyond the schema, so the baseline of 3 is appropriate.

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?

The description clearly states the tool lists asynchronous operation commands against a workload or volumeset, enumerates specific command types, and distinguishes from the sibling tool get_command by noting 'Use get_command for one command’s full status.' This is a specific verb-plus-resource with clear sibling differentiation.

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?

It specifies required parameters (kind, gvc, name) and an optional filter (lifecycleStage), and explicitly directs users to get_command for single-command details. While it doesn't list exclusions (e.g., when not to use), the guidance is clear and actionable, earning above-average but not perfect.

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

All Control Plane toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Every tool targets a distinct resource/action pair (e.g., get_resource vs get_resource_schema, list_deployments vs list_workload_replicas) and descriptions clearly differentiate purposes. No two tools appear to do the same thing.

Naming Consistency5/5

All tools follow a verb_noun snake_case pattern (create_gvc, update_workload, list_resources, query_metrics) with consistent verbs. The few imperative verbs (browse, build, mount) still maintain the same verb-first structure.

Tool Count1/5

With 55 tools, this server far exceeds the typical well-scoped 3-15 tool range. While each tool appears purposeful, the sheer number creates selection overhead and falls into the extreme 50+ category on the rubric.

Completeness4/5

The surface covers nearly the full Control Plane lifecycle: CRUD for GVC, workload, identity, policy, volumeset, and domain, plus observability, templates, image builds, and Terraform. Minor gaps include referenced but missing configure_workload_* tools and no secret creation/deletion (by design).

Resources