Skip to main content
Glama
RawTree MCP Server

RawTree MCP Server

Official
by rawtreedb

Get Connector

get-connector
Read-only

Retrieve a managed connector's status, sanitized settings, destinations, revision, and timestamps to inspect its current setup before adding a destination or changing status.

Instructions

Purpose: Get one managed connector and its complete public configuration.

Returns: The connector status, sanitized connection settings, destinations with their source configuration, revision, and timestamps. Stored credentials are never returned.

When to use: Inspect the latest connector before adding a destination or changing its status.

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

Input Schema

NameRequiredDescriptionDefault
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.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 meaningfully beyond them: it enumerates what is returned (status, sanitized settings, destinations with source config, revision, timestamps) and explicitly states credentials are never returned. It does not cover failure behavior for a missing or unauthorized connector, which keeps it just under 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three bolded, front-loaded sections covering purpose, returns, and timing; every sentence carries information, and the detail in Returns is justified because no output schema exists.

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?

With no output schema, the description compensates well by describing the return payload and the credential-sanitization guarantee, and the annotations handle the safety profile. Minor omissions remain around error conditions and whether the connector must exist in the given cluster/organization.

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 connectorId, cluster, and organization are already documented in the schema. The description adds no syntax, defaulting, or scoping detail for cluster/organization, so the 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?

The description opens with a specific verb and resource ('Get one managed connector') and delimits scope with 'one' and 'complete public configuration', which separates it from the list-connectors tool referenced in the connectorId parameter. The 'When to use' line further situates it relative to destination-adding and status-changing operations.

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?

It gives an explicit usage moment: inspect the latest connector before adding a destination or changing status, which points an agent toward the follow-up tools. It does not state when NOT to use it (e.g., when only a list summary is needed) or name the alternative retrieval tools outright, so it stops short of full routing guidance.

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