Skip to main content
Glama
RawTree MCP Server

RawTree MCP Server

Official
by rawtreedb

Get Workflow

get-workflow
Read-onlyIdempotent

Retrieves a workflow's details, query, schedule, revision, sinks, and timestamps so you can inspect its current configuration and schedule.

Instructions

Read a workflow and its current schedule configuration. Returns the workflow object: id, name, description, query, schedule, revision, created_at, updated_at, and sinks. The query object contains database and sql. schedule is null for manual-only workflows; otherwise it contains cron, enabled, and next_run_at (null while paused). Each sink has id, type, and settings. HTTP settings contain url (null when unreadable), url_configured, and header_names; header values are never returned. Table settings contain database and table. Slack settings contain integration_id, channel_id, and channel_name, resolved from Slack when the sink was saved. Requires an admin API key bound to the selected organization and cluster, or OAuth. Organization members may read; organization admins may create, update, or delete. Workflows execute with organization credentials and continue after the creating key is revoked or expires.

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": {
      "organization": "<organization>",
      "cluster": "<cluster>",
      "id": "<id>"
    },
    "name": "get-workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWorkflow ID returned by list-workflows, get-workflow, or create-workflow.
clusterYesRawTree cluster to use for this operation.
organizationYesRawTree organization containing the target cluster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.2

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, it discloses important behavioral details: schedule is null for manual-only workflows, next_run_at is null while paused, url is null when unreadable, and header values are never returned. It also explains that workflows execute with organization credentials and persist after the creating key is revoked, which materially shapes how an agent should treat this resource.

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 purpose is front-loaded in the first sentence, followed by a dense but organized field-by-field breakdown of the return object. It is long, but nearly every clause conveys a distinct fact (null semantics, security redaction, permission model); some field enumeration could be deferred to an output schema that does not currently exist.

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?

With no output schema, the description carries the full burden of describing the return shape, and it does so comprehensively for the workflow object, query, schedule, and the three sink setting variants. Permission and credential requirements are also covered, leaving little an agent needs to call it correctly.

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%, so id, cluster, and organization are already documented in the schema. The description reinforces that the organization and cluster must be the ones the credential is bound to, but adds no new syntax or constraints beyond that; baseline 3 applies when the schema carries the load.

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 opens with a specific verb and resource: 'Read a workflow and its current schedule configuration,' and immediately enumerates the returned fields. An agent can distinguish this singular read from list-workflows by the required 'id' parameter and the singular object return, though no sibling is named explicitly.

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 states the credential prerequisites ('Requires an admin API key bound to the selected organization and cluster, or OAuth') and the read/write permission split between members and admins. It does not, however, explicitly route the agent away from list-workflows or create/update-workflow, leaving the choice to be inferred from the singular read semantics.

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