Skip to main content
Glama
RawTree MCP Server

RawTree MCP Server

Official
by rawtreedb

Verify Cluster S3 Access

verify-cluster-s3-access
Idempotent

Verifies that RawTree can assume your IAM role and access customer-owned S3 data and backup buckets before cluster creation, including read/write probe checks.

Instructions

Purpose: Verify that RawTree can use a customer IAM role to access customer-owned S3 storage before cluster creation.

Returns: Whether access was verified and a human-readable result message.

Behavior: RawTree assumes roleArn using s3StorageAccess.externalId, checks the data and backup bucket locations, lists each configured path, and writes, reads, then removes a temporary probe object under each path. Paths are optional and default to the bucket root. Both configured buckets must be in the cluster environment's AWS region.

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

When to use: Use this tool after the IAM trust and permissions policies are configured and immediately before create-cluster whenever its optional s3Storage field will be provided. It is unnecessary when RawTree-managed storage will be used.

Safety: This check temporarily writes to and deletes from both configured destinations. Confirm the exact organization, buckets, paths, role ARN, and External ID before running it. The IAM trust policy's External ID must match s3StorageAccess.externalId exactly.

Reliability: The check is safe to retry. Newly changed IAM policies may require a short propagation delay before verification succeeds.

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>",
      "s3StorageAccess": "<s3StorageAccess>",
      "s3Storage": "<s3Storage>"
    },
    "name": "verify-cluster-s3-access"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionIdNoRegion ID returned by list-cluster-regions. Use the same region for sizes, S3 verification and creation.
s3StorageYesCustomer-owned S3 configuration to verify before cluster creation.
organizationYesOrganization that will own the cluster.
s3StorageAccessYes

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. Changed16 schema fields changedv0.4.2
    • addedInput schema / additionalProperties
      Added value: +false
    • 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"
      +}
    • addedInput schema / properties / s3Storage / additionalProperties
      Added value: +false
    • addedInput schema / properties / s3Storage / properties / backups / additionalProperties
      Added value: +false
    • changedInput schema / properties / s3Storage / properties / backups / description
      Previous value: -"Customer-owned bucket and optional key prefix for backups."New value: +"Destination for backups."
    • addedInput schema / properties / s3Storage / properties / backups / properties / bucket / description
      Added value: +"Customer-owned S3 bucket."
    • addedInput schema / properties / s3Storage / properties / backups / properties / path / description
      Added value: +"Optional object-key prefix; defaults to the bucket root."
    • addedInput schema / properties / s3Storage / properties / data / additionalProperties
      Added value: +false
    • changedInput schema / properties / s3Storage / properties / data / description
      Previous value: -"Customer-owned bucket and optional key prefix for data."New value: +"Destination for table data."
    • addedInput schema / properties / s3Storage / properties / data / properties / bucket / description
      Added value: +"Customer-owned S3 bucket."
    • addedInput schema / properties / s3Storage / properties / data / properties / path / description
      Added value: +"Optional object-key prefix; defaults to the bucket root."
    • removedInput schema / properties / s3Storage / properties / externalId
      Removed value: -{
      -  "description": "External ID required by the IAM role trust policy. It must exactly match the value configured in AWS.",
      -  "maxLength": 1224,
      -  "minLength": 2,
      -  "pattern": "^[A-Za-z0-9_+=,.@:/-]+$",
      -  "type": "string"
      -}
    • changedInput schema / properties / s3Storage / properties / roleArn / description
      Previous value: -"ARN of the customer IAM role that RawTree may assume to access the configured buckets."New value: +"ARN of the customer IAM role RawTree may assume."
    • changedInput schema / properties / s3Storage / required
      Previous value: -[
      -  "data",
      -  "backups",
      -  "roleArn",
      -  "externalId"
      -]New value: +[
      +  "data",
      +  "backups",
      +  "roleArn"
      +]
    • addedInput schema / properties / s3StorageAccess
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "externalId": {
      +      "description": "Immutable cluster External ID. Use this exact value in customer IAM role trust policies.",
      +      "maxLength": 1224,
      +      "minLength": 2,
      +      "pattern": "^[A-Za-z0-9_+=,.@:/-]+$",
      +      "type": "string"
      +    },
      +    "resourceTag": {
      +      "description": "Immutable rawtree.com/cluster tag value for S3 storage access. Generated by the API when omitted.",
      +      "maxLength": 256,
      +      "minLength": 1,
      +      "pattern": "^[a-z0-9][a-z0-9-]*$",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "externalId"
      +  ],
      +  "type": "object"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "organization",
      -  "s3Storage"
      -]New value: +[
      +  "organization",
      +  "s3StorageAccess",
      +  "s3Storage"
      +]
  3. Addedv0.3.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true; the description explains why by disclosing the assume-role call, path listing, and a write/read/delete probe object under each path. It also adds non-obvious constraints beyond annotations: both buckets must be in the cluster environment's AWS region, org-admin token required, and newly changed IAM policies may need propagation delay. The self-created probe deletion is consistent with destructiveHint=false, so no contradiction.

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?

The labeled sections (Purpose/Returns/Behavior/Auth/When to use/Safety/Reliability) make it easy to scan and the purpose plus routing guidance is front-loaded. It is longer than strictly necessary — the Returns line and the path-default sentence partially repeat structured or schema content — but no section is filler for a tool with this much pre-flight risk.

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?

For a 4-parameter tool with nested objects, a mutation side effect, and no output schema, the description covers the return shape, auth requirements, side effects, region constraint, and retry behavior. An agent has everything needed to call it correctly and to warn the user about temporary writes.

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

Parameters4/5

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

Schema coverage is 75%, so most fields are documented; the description still adds meaning the schema lacks, notably the region-coherence rule tying both buckets to the cluster environment's region and the requirement that the IAM trust policy's External ID match s3StorageAccess.externalId exactly. It reinforces that paths are optional and default to the bucket root, which is already in the schema, so it stops short of full compensation for the undocumented remainder.

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 ('Verify that RawTree can use a customer IAM role to access customer-owned S3 storage') and scopes it to 'before cluster creation', which distinguishes it from the sibling verify-database-s3-access. An agent can tell what it does and where it sits in the workflow without opening the schema.

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 explicit when-to-use ('after the IAM trust and permissions policies are configured and immediately before create-cluster whenever its optional s3Storage field will be provided') and an explicit when-not ('unnecessary when RawTree-managed storage will be used'). The alternative path is named, so no inference is required.

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