Skip to main content
Glama
Sign In
@callirra/mcp

@callirra/mcp

Official
by callirra-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_workflow_run

Read-onlyIdempotent

Retrieve an existing workflow run by ID to inspect its steps, credits, and outputs, so you can review execution results and troubleshoot workflows.

Instructions

Read an existing workflow run, steps, credits and outputs.

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": {
      "id": "<id>"
    },
    "name": "get_workflow_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful return-content context by naming steps, credits, and outputs, but does not disclose permission requirements, behavior for missing runs, or error conditions.

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?

The description is a single efficient sentence with the core operation and returned data front-loaded. There is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with rich read-only annotations and no output schema, the description adequately states what is returned. However, the lack of ID semantics leaves a meaningful gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, "id," with 0% schema description coverage, and the description does not clarify whether this is a workflow run ID, project ID, or another identifier format. With low schema coverage, the description should compensate but does not.

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 gives a specific verb and resource: "Read an existing workflow run," and names the returned data: steps, credits, and outputs. It is clearly distinct from create/list/wait/cancel workflow-run siblings by resource and operation, though it does not explicitly call out those alternatives.

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 phrase "existing workflow run" implies this is a retrieval tool used after a run has been created, but there is no explicit guidance on when to use it versus list_workflow_runs, wait_workflow_run, or create_workflow_plan. Usage is inferable rather than stated.

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