Skip to main content
Glama
RawTree MCP Server

RawTree MCP Server

Official
by rawtreedb

Add Connector Destination

add-connector-destination
Idempotent

Add a Kafka topic-to-table or NATS JetStream consumer-to-table destination to an existing connector without changing its current destinations.

Instructions

Purpose: Add one Kafka topic-to-table or NATS JetStream consumer-to-table destination to an existing connector without changing its current destinations.

Behavior: The tool reads the latest connector, preserves every existing destination, and appends the new destination. For Kafka, omit group_id to generate an independent consumer group. For NATS, supply nats_stream and nats_consumer for an existing durable pull consumer with explicit acknowledgements. An exact existing database/table destination is treated as an idempotent success; conflicting settings are rejected.

Auth: Requires organization-admin access.

Safety: Confirm the exact organization, cluster, connector ID, source topics or stream, consumer group or durable consumer, database, and table before calling.

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": {
      "connectorId": "<connectorId>",
      "destination": "<destination>"
    },
    "name": "add-connector-destination"
  }
}

Input Schema

NameRequiredDescriptionDefault
clusterNoRawTree cluster to use for this operation.
connectorIdYesConnector ID returned by list-connectors or create-connector.
destinationYes
organizationNoRawTree organization containing the target cluster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.4.9
    • removedInput schema / properties / destination / additionalProperties
      Removed value: -false
    • addedInput schema / properties / destination / anyOf
      Added value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "database": {
      +        "description": "Destination RawTree database.",
      +        "pattern": "^[A-Za-z][A-Za-z0-9_]{0,63}$",
      +        "type": "string"
      +      },
      +      "group_id": {
      +        "description": "Kafka consumer group. Omit to let RawTree generate an independent group for this destination.",
      +        "maxLength": 255,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "table": {
      +        "description": "Destination RawTree table.",
      +        "pattern": "^[A-Za-z][A-Za-z0-9_]{0,63}$",
      +        "type": "string"
      +      },
      +      "topics": {
      +        "description": "Kafka topics consumed by this destination.",
      +        "items": {
      +          "minLength": 1,
      +          "type": "string"
      +        },
      +        "maxItems": 100,
      +        "minItems": 1,
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "topics",
      +      "database",
      +      "table"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "database": {
      +        "description": "RawTree database or table identifier.",
      +        "pattern": "^[A-Za-z][A-Za-z0-9_]{0,63}$",
      +        "type": "string"
      +      },
      +      "nats_consumer": {
      +        "description": "Existing durable pull consumer with explicit acknowledgements.",
      +        "maxLength": 255,
      +        "minLength": 1,
      +        "pattern": "^[^\\s.*>/\\\\]+$",
      +        "type": "string"
      +      },
      +      "nats_stream": {
      +        "description": "Existing JetStream stream name.",
      +        "maxLength": 255,
      +        "minLength": 1,
      +        "pattern": "^[^\\s.*>/\\\\]+$",
      +        "type": "string"
      +      },
      +      "table": {
      +        "description": "RawTree database or table identifier.",
      +        "pattern": "^[A-Za-z][A-Za-z0-9_]{0,63}$",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "nats_stream",
      +      "nats_consumer",
      +      "database",
      +      "table"
      +    ],
      +    "type": "object"
      +  }
      +]
    • removedInput schema / properties / destination / properties
      Removed value: -{
      -  "database": {
      -    "description": "Destination RawTree database.",
      -    "pattern": "^[A-Za-z][A-Za-z0-9_]{0,63}$",
      -    "type": "string"
      -  },
      -  "group_id": {
      -    "description": "Kafka consumer group. Omit to let RawTree generate an independent group for this destination.",
      -    "maxLength": 255,
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  "table": {
      -    "description": "Destination RawTree table.",
      -    "pattern": "^[A-Za-z][A-Za-z0-9_]{0,63}$",
      -    "type": "string"
      -  },
      -  "topics": {
      -    "description": "Kafka topics consumed by this destination.",
      -    "items": {
      -      "minLength": 1,
      -      "type": "string"
      -    },
      -    "maxItems": 100,
      -    "minItems": 1,
      -    "type": "array"
      -  }
      -}
    • removedInput schema / properties / destination / required
      Removed value: -[
      -  "topics",
      -  "database",
      -  "table"
      -]
    • removedInput schema / properties / destination / type
      Removed value: -"object"
  2. Addedv0.3.2

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses the read-modify-append implementation, that existing destinations are preserved, that an exact duplicate destination is treated as idempotent success while conflicting settings are rejected, and that organization-admin access is required. These are exactly the mutation semantics an agent needs and are not derivable from readOnlyHint/idempotentHint/destructiveHint alone.

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/Behavior/Auth/Safety) front-load the essentials and make scanning easy. The Safety line is largely generic caution rather than tool-specific information, which is mild padding, but the whole text stays reasonably tight.

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?

For a non-destructive, idempotent mutation tool with no output schema, the definition covers auth, idempotency, conflict handling, and per-variant parameter semantics. It does not say what the call returns or how to verify the result (e.g., via get-connector), which is the remaining gap.

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% and the description reinforces the key semantic behaviors: omitting group_id generates an independent consumer group, and NATS requires an existing durable pull consumer with explicit acknowledgements. Most of this overlaps the schema's own property descriptions, so the added value is moderate rather than substantial.

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: 'Add one Kafka topic-to-table or NATS JetStream consumer-to-table destination to an existing connector.' It also scopes the operation ('without changing its current destinations'), which distinguishes it from create-connector and any full-replacement update.

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?

Gives clear context: use this on an existing connector, with conditional guidance per source type (Kafka: omit group_id; NATS: supply nats_stream and nats_consumer on an existing durable pull consumer). It does not name an alternative sibling (e.g., create-connector or a connector-update tool) or state when not to use it.

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