Skip to main content
Glama
RawTree MCP Server

RawTree MCP Server

Official
by rawtreedb

List Clusters

list-clusters

List RawTree dedicated clusters in an organization to retrieve cluster IDs, names, lifecycle status, resources, and storage metadata for discovery or provisioning checks.

Instructions

Purpose: List RawTree dedicated clusters accessible in an organization.

Returns: Cluster IDs, names, creation times, lifecycle status, resources, whether each cluster can be paused or resumed, optional s3_storage metadata for customer-owned default storage, and s3_storage_access containing external_id and resource_tag (null for older clusters without saved identity). s3_storage exposes data and backups, each with bucket and path. An empty path means the bucket root. Role ARNs and secret credentials are never returned.

With user authentication, discovery spans enabled regions. If a region is unavailable, healthy clusters are returned with unavailable_regions (region IDs and names). This is a partial list: do not infer that missing clusters do not exist; retry discovery. Each regional lookup is limited to five seconds. Authentication failures and total regional outages remain errors.

Auth: The RawTree API requires a user access token and organization membership. Authorization is enforced by the API.

When to use:

  • User asks which dedicated clusters exist

  • You need a cluster ID or current lifecycle status

  • You need to inspect provisioned resources before creating another cluster

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organization": "<organization>"
    },
    "name": "list-clusters"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationYesOrganization whose dedicated clusters should be listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.2

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it enumerates the returned fields, discloses that role ARNs and secrets are never returned, warns that results can be a partial list with unavailable_regions and that five-second per-region lookups apply, and states which conditions still error. This is exactly the behavioral context an agent needs beyond structured fields.

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?

Bold-labeled sections (Purpose / Returns / Auth / When to use) with purpose front-loaded make it scannable. It is on the long side and the nested s3_storage field walkthrough is dense, but since no output schema exists, that detail earns most of its space.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description fully compensates by describing the return payload, null/empty-path semantics, partial-result behavior, and error conditions. Combined with the auth requirements, an agent has everything needed to call this correctly and interpret the result.

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% for the single `organization` parameter, so the schema already defines its meaning. The description reinforces the org-scoping constraint ("accessible in an organization") but adds no format or lookup guidance beyond that, making the baseline 3 correct.

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?

States a specific verb and resource ("List RawTree dedicated clusters") plus the scope ("accessible in an organization"). Plural list scope makes it naturally distinct from get-cluster (single cluster), list-cluster-sizes and create-cluster without needing to name them.

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?

The "When to use" block gives three concrete triggering conditions: existence questions, needing a cluster ID/lifecycle status, and inspecting resources before creating another cluster. It lacks explicit exclusions or sibling routing (e.g. "for one cluster's details use get-cluster"), so it stops short of a 5.

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