Skip to main content
Glama
Sign In
RawTree MCP Server

RawTree MCP Server

Official
by rawtreedb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Integrations

list-integrations
Read-onlyIdempotent

Lists Slack workspaces connected to a RawTree organization and returns integration IDs for workflow sinks. Use it to check Slack availability and share the settings URL when no workspace is connected.

Instructions

Purpose: List the integrations connected to a RawTree organization, such as Slack workspaces.

Returns: { integrations, slack_available, settings_url }. Each integration has id, organization_id, type ("slack"), settings (team_id, team_name, bot_user_id, scopes), and created_at. slack_available is false when Slack is not configured for this RawTree deployment. settings_url links to the organization's integrations settings page in the RawTree app.

Behavior: Connecting or disconnecting Slack is not available through MCP: an organization admin must do it on the integrations settings page in the RawTree app. Share settings_url with the user when no Slack workspace is connected.

Auth: Requires a user credential such as OAuth and membership in the organization. API keys are not supported. Authorization is enforced by the RawTree API.

When to use:

  • You need a Slack integration ID for a workflow Slack sink

  • The user wants to know which Slack workspaces the organization has connected

Input Schema

NameRequiredDescriptionDefault
organizationYesOrganization whose integrations should be used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.3

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses authentication requirements (user OAuth and organization membership, no API keys), the exact return fields, the meaning of slack_available, and the settings_url fallback behavior. This is substantial operational context that an agent could not infer from the annotations or schema.

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 description is structured with clear Purpose, Returns, Behavior, Auth, and When to use sections, and it is front-loaded with the core purpose. It is somewhat long for a one-parameter list tool, but most of the detail is useful given the absence of an output schema.

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?

The tool has no output schema, but the description supplies the return shape, auth requirements, behavioral limitations, and usage scenarios. An agent has everything needed to call it correctly and interpret the response.

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 coverage is 100% for the single organization parameter, so the schema already explains it adequately. The description adds that the organization must be one the user belongs to, but this is auth context rather than parameter-level meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: list integrations connected to a RawTree organization, with Slack workspaces as the concrete example. It is clear what the tool does, but it does not explicitly contrast itself with sibling tools such as list-slack-channels.

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 'When to use' section gives two concrete scenarios, and the behavior section explains that connecting or disconnecting Slack cannot be done through MCP. This covers when to use and when not to use the tool, though it does not name direct alternative tools.

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