Skip to main content
Glama
RawTree MCP Server

RawTree MCP Server

Official
by rawtreedb

List Cluster Sizes

list-cluster-sizes
Read-only

Retrieve current cluster creation options, including supported per-replica sizes, replica count limits, and default vertical autoscaling ranges before creating a cluster.

Instructions

Purpose: List the current RawTree cluster creation options.

Returns: Supported per-replica sizes, minimum and maximum replica counts, and the default minimum and maximum vertical autoscaling sizes.

Auth: Requires a user credential such as OAuth. Authorization is enforced by the RawTree API.

When to use: You MUST call this tool before create-cluster so replicas and both sizes come from the current backend-controlled catalog.

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-cluster-sizes"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionIdNoRegion ID returned by list-cluster-regions. Use the same region for sizes, S3 verification and creation.
organizationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.5
    • changedInput schema / properties / regionId / description
      Previous value: -"Region ID returned by list-regions. Use the same region for sizes, S3 verification and creation. Omit for the default backend."New value: +"Region ID returned by list-cluster-regions. Use the same region for sizes, S3 verification and creation."
  2. Changed2 schema fields changedv0.4.2
    • addedInput schema / properties / organization
      Added value: +{
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / regionId
      Added value: +{
      +  "description": "Region ID returned by list-regions. Use the same region for sizes, S3 verification and creation. Omit for the default backend.",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
  3. Addedv0.3.2

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 value beyond that by disclosing the auth requirement (user credential such as OAuth, enforced by the RawTree API) and describing the returned content in the absence of an output schema.

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 section headers (Purpose, Returns, Auth, When to use) make it easy to scan and the key constraint is front-loaded. It is slightly longer than necessary for a read-only catalog lookup, but no sentence is 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?

With no output schema, the Returns section correctly compensates by naming what comes back, and auth plus prerequisite ordering are covered. The only gap is the unexplained 'organization' parameter, which matters since callers must know how to scope the catalog lookup.

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

Parameters2/5

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

The description says nothing about the two parameters. The schema covers regionId thoroughly (including cross-referencing list-cluster-regions), but at 50% coverage the undescribed 'organization' parameter is left undocumented in both schema and description, and the description does nothing to compensate.

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 the current RawTree cluster creation options') and the Returns section enumerates exactly what is produced: per-replica sizes, min/max replica counts, and vertical autoscaling defaults. This distinguishes it clearly from siblings like list-clusters and list-cluster-regions, which return different resources.

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

Usage Guidelines5/5

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

Gives an explicit, mandatory usage rule: 'You MUST call this tool before create-cluster so replicas and both sizes come from the current backend-controlled catalog.' It names the dependent tool and the reason, leaving no inference needed about sequencing.

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