Skip to main content
Glama
Sign In

busabase

by com.busabase
OverviewDiscussionsAdmin

Get a workflow run

workflows_get
Read-only

One run, with every finished step's snapshot.

GET /api/v1/workflow-runs/{runId}

For multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId. A workflow run can call webhooks and functions and create, change, or delete records. It acts as this key's owner but never beyond this key's permission level. If the key is revoked, expires, or is lowered while a run waits, the run fails instead of carrying on.

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": {
      "runId": "<runId>"
    },
    "name": "workflows_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYes
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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, so the safety profile is covered; the description adds genuinely new context: a run may invoke webhooks/functions and mutate records, acts as the key owner but capped by key permissions, and fails rather than continuing if the key is revoked/expired/downgraded mid-wait. The phrase "every finished step's snapshot" also signals that pending steps may lack snapshots, which is meaningful output behavior.

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?

Front-loaded with the one-line purpose and endpoint, then the space caveat, then the run-semantics context. Every sentence carries distinct information with no repetition.

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 two-parameter read tool with no output schema and existing annotations, the description covers the main gotcha (multi-space targeting) and clarifies what a run does. Minor gaps remain around what is returned for unfinished/failed steps and any error or access-denied behavior.

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 50%: targetSpaceId is already documented in the schema in nearly the same words used in the description, so that guidance is largely duplicated. runId, the required parameter, gets no explanation beyond its name, though its meaning is self-evident from the endpoint path.

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?

"One run, with every finished step's snapshot" plus the concrete endpoint GET /api/v1/workflow-runs/{runId} makes it unambiguous that this fetches a single workflow run and its step snapshots. It implicitly contrasts with the list-style siblings (workflows_list) by emphasizing "one run," but never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a concrete procedural rule for multi-space accounts (call auth_verify, ask the user, pass targetSpaceId), which is real usage guidance. However, it never states when to reach for this tool versus workflows_list, workflows_decide, or workflows_cancel, so routing between siblings is left to inference.

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

All busabase toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources