Skip to main content
Glama
RawTree MCP Server

RawTree MCP Server

Official
by rawtreedb

Set Connector Status

set-connector-status
DestructiveIdempotent

Pause or resume all destinations in a connector to control ingestion: paused removes it from active runtime; active restores consumers and resumes delivery.

Instructions

Purpose: Pause or resume every destination in one connector.

Behavior: paused removes the connector from the active runtime. active restores it with the same Kafka consumer groups or NATS durable consumers. Resumption depends on broker retention and saved consumer progress; delivery is at least once.

Auth: Requires organization-admin access.

Safety: Confirm the exact organization, cluster, connector ID, and requested status. Pausing interrupts ingestion for all destinations until resumed.

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>",
      "status": "<status>"
    },
    "name": "set-connector-status"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 (destructiveHint=true, idempotentHint=true), the description explains what actually happens: paused removes the connector from the active runtime, active restores it with the same Kafka consumer groups or NATS durable consumers, resumption depends on broker retention and saved progress, and delivery is at-least-once. It also discloses the org-admin auth requirement and the ingestion interruption window, which annotations alone cannot convey.

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 bolded Purpose/Behavior/Auth/Safety structure is front-loaded and scannable, with each block carrying distinct information. Slight redundancy exists where the safety line repeats the parameter names, but nothing is pure 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?

For a destructive state-changing tool with no output schema, the definition covers purpose, runtime effects, auth, and preconditions well. The only gap is that it does not hint at what the call returns (e.g., resulting status or confirmation), leaving the agent to infer the response shape.

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 parameters are already documented, but the description adds real semantic meaning to the 'status' enum by explaining what active and paused each do at runtime, plus the scope implied by connectorId ('every destination in one connector'). The organization and cluster parameters are only implicitly referenced via the safety confirmation line.

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?

The first line states a specific verb pair and resource ('Pause or resume every destination in one connector'), including the scope that the whole connector is affected rather than a single destination. This distinguishes it from sibling tools like add-connector-destination or get-connector without the agent needing to open a schema.

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?

The description gives clear operating context: organization-admin auth is required, and the safety line instructs the caller to confirm organization, cluster, connector ID, and requested status before acting. It also warns that pausing interrupts ingestion. It stops short of naming an alternative tool or an explicit when-not condition, so it falls below the top mark.

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