Skip to main content
Glama

list_clusters

Read-onlyIdempotent

List compute clusters and their current state within a workspace. Use it to check cluster availability before running jobs or to verify workspace compute capacity.

Instructions

List compute clusters and their state.

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

Input Schema

NameRequiredDescriptionDefault
workspaceNoNamed workspace. Omit to use the default workspace.

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, destructiveHint=false, and openWorldHint=false, so safety is fully covered. The description adds only that cluster state is returned, but says nothing about whether terminated clusters are included, pagination, or result ordering.

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?

One front-loaded sentence with no filler. It is arguably under-specified rather than verbose, so the terseness is efficient but borders on insufficient.

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?

A zero-required-parameter, read-only list tool is simple, and annotations plus the fully documented parameter cover most of what an agent needs. Still missing is any indication of what 'state' values look like or whether output is scoped to one workspace, which matters for a cluster inventory tool.

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 the single 'workspace' parameter is documented as omitting to use the default. The description adds no meaning beyond that, so the schema carries the burden and 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?

Specific verb ('List') plus resource ('compute clusters') and a hint at payload ('their state'). It does not distinguish itself from siblings such as start_cluster or terminate_cluster, so an agent must infer that this is the read-only enumeration counterpart.

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?

No when-to-use or when-not-to-use guidance is given. With sibling tools like start_cluster, terminate_cluster, and list_workspaces present, the description never tells an agent that this is the discovery step before lifecycle operations or how it relates to workspace scoping.

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