Skip to main content
Glama
rawtreedb

RawTree MCP Server

Official
by rawtreedb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Cluster Sizes

list-cluster-sizes
Read-only

Purpose: List the current RawTree cluster creation options.

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.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. 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, and the description adds genuine context beyond them: the auth requirement (OAuth user credential, API-enforced authorization) and the fact that values are backend-controlled and therefore may change. It does not cover caching or whether the catalog varies by region, which would have pushed it to a 5.

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?

Front-loaded with a bolded Purpose line, then Returns, Auth, and When-to-use in priority order — easy to scan. Slightly verbose with four labeled sections for a two-parameter read tool, 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?

A read-only catalog tool with no output schema needs its return shape and ordering constraint explained, and both are. The remaining gap is the undocumented 'organization' parameter and how the catalog differs per region, which an agent may need in a multi-tenant or multi-region call.

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?

Schema coverage is 50% and the description says nothing about either parameter. regionId is self-documented in the schema, but 'organization' has no description anywhere, and the description does not explain the default-backend behavior for omitted regionId beyond what the schema already states.

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 explicitly enumerates what the catalog contains (per-replica sizes, min/max replica counts, default autoscaling bounds). This clearly separates it from list-clusters, get-cluster, and list-regions.

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, hard prerequisite: 'You MUST call this tool before create-cluster so replicas and both sizes come from the current backend-controlled catalog.' The alternative path (hardcoding values) is implicitly ruled out, which is exactly the routing information an agent needs.

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

Deploy Server

Other Tools