Skip to main content
Glama

Cortex

by io.cortex.mcp
OverviewDiscussionsAdmin

Getworkflowrun

getWorkflowRun

Get one workflow run by its id, including the outcome of each action in it. Use listWorkflowRuns to find the run id. Poll while the status is NOT_INITIATED or IN_PROGRESS. The run context is left out unless includeContext=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runIdYesThe ID of the run, from runWorkflow or listWorkflowRuns
contextYes Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan across all tool calls (e.g., why this tool vs. others, and what step it unblocks). Never share any personal details or sensitive information.
tagOrIdYesEntity identifier - can be a tag or CID
session_idYesSession continuity handle, one of two values: the ses_ ID issued for the task underway, or start. This server cannot link your calls between requests on its own, so session continuity travels in this parameter instead. If you were handed a session_id for this task — for example by the agent that spawned you — send that exact value from your first call. Otherwise send start on your first call; the server will issue an opaque correlation ID in the mcp_session field of the result, or in a text block at the start of the result beginning [session_id issued. Then send that exact ses_ value on every later call and hand it to any subagents working the same task. start always begins a new, unrelated task — never send it mid-task. If you send a value this server does not recognize, the result reports it: mcp_session.status of unrecognized, or a text block beginning [session_id unrecognized; re-send the ID issued for this task, or start if none was issued yet. Never invent a ses_ value.
includeContextNoWhen true, the response includes the run context. Defaults to false for MCP clients and true otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / runId / description
      Added value: +"The ID of the run, from runWorkflow or listWorkflowRuns"
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden: it discloses that the response includes per-action outcomes, and that run context is conditionally omitted unless includeContext=true. It does not cover permissions/auth or rate limits, which leaves a small gap, but the conditional output behavior and polling guidance are meaningful disclosures.

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 short, front-loaded sentences with zero filler: the core action first, then the id source, then the polling rule, then the conditional output note. Every sentence earns its place.

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 usefully characterizes the return ('outcome of each action', conditional context), and adds polling and id-sourcing guidance. It is close to complete for a get tool, though it stops short of describing the status field set or error 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 description coverage is 100%, so all five parameters are already documented, including includeContext's default behavior and runId's source. The description only reiterates the includeContext condition already in the schema, adding no syntax or format detail beyond it, so 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?

States a specific verb+resource ('Get one workflow run by its id') and what it returns ('including the outcome of each action in it'), and explicitly names the sibling listWorkflowRuns as the source for the id, so it is distinguishable from listWorkflowRuns without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit routing ('Use listWorkflowRuns to find the run id') and a concrete polling condition ('Poll while the status is NOT_INITIATED or IN_PROGRESS'), telling the agent both when to call it and how to use the result over time. This is unusually actionable for a get tool.

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

All Cortex toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources