Skip to main content
Glama
rawtreedb

RawTree MCP Server

Official
by rawtreedb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete API Key

delete-api-key
Destructive

Permanently revoke and delete a RawTree API key by UUID or full API key value. Use to remove compromised or unused keys; services using the key lose access.

Instructions

Purpose: Permanently revoke and delete a RawTree API key by UUID or full API key value.

NOT for: Deleting a table, database, or user session.

Returns: Deletion confirmation.

Safety: You MUST list or identify the key first, ask the user to confirm the exact key name or ID, and warn that services using it will lose access. This action cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clusterNoRawTree cluster to use for this operation.
idOrApiKeyYesAPI key UUID or full rt_ API key value to delete.
organizationNoRawTree organization containing the target cluster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / cluster
      Added value: +{
+  "description": "RawTree cluster to use for this operation.",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Set to true only after the user explicitly confirms revocation of this exact API key.",
-  "type": "boolean"
-}
    • addedInput schema / properties / organization
      Added value: +{
+  "description": "RawTree organization containing the target cluster.",
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "idOrApiKey",
-  "confirm"
-]New value: +[
+  "idOrApiKey"
+]
  2. Changed3 schema fields changedv0.2.0
    • addedInput schema / properties / idOrApiKey
      Added value: +{
+  "description": "API key UUID or full rt_ API key value to delete.",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / idOrToken
      Removed value: -{
-  "description": "API key UUID or full rt_ token to delete.",
-  "minLength": 1,
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "idOrToken",
-  "confirm"
-]New value: +[
+  "idOrApiKey",
+  "confirm"
+]
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description goes further by disclosing irreversibility ('This action cannot be undone'), the downstream consequence (services using the key lose access), the accepted key formats, and a required confirmation protocol. This is exactly the extra context annotations cannot carry.

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 labels (Purpose/NOT for/Returns/Safety) front-load the essential facts and make scanning easy, with each block contributing distinct information. The formatting is slightly heavier than a two-sentence description would need, but nothing is filler.

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 destructive, no-output-schema tool, the description covers return value ('Deletion confirmation'), safety profile, identifier formats, and scope exclusions. An agent has everything needed to invoke it correctly and responsibly.

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%, so cluster, organization, and idOrApiKey are already documented. The description restates that the key may be given as a UUID or a full rt_ value, which mirrors the schema rather than adding new semantics; baseline 3 applies.

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+resource ('Permanently revoke and delete a RawTree API key') and names the accepted identifier forms (UUID or full rt_ key value). The 'NOT for' line explicitly excludes sibling operations like delete-table, delete-database, and session deletion, so the agent can disambiguate from the many delete/list siblings without opening schemas.

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?

Explicitly says when not to use it (tables, databases, sessions) and prescribes a mandatory pre-flight workflow: list/identify the key first, obtain user confirmation of the exact name or ID, and warn about access loss. There is no reliance on inference.

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