Skip to main content
Glama
Sign In
cc-agent

cc-agent

by Gonzih
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_workflow_status

Poll a workflow's status to retrieve its goal, stage breakdown, and per-step job IDs and statuses.

Instructions

Poll the status of a workflow created by generate_workflow. Returns goal, stage breakdown, per-step job IDs and statuses.

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": {
      "workflow_id": "<workflow_id>"
    },
    "name": "get_workflow_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflow_idYesWorkflow ID returned by generate_workflow

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.15

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided. Description indicates a polling operation but does not disclose side effects, rate limits, or safety beyond the implied read-only nature. It adds minimal behavioral context beyond the basics.

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?

Two sentences delivering the core purpose and return value with no unnecessary words.

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?

For a simple polling tool with one parameter and no output schema, the description fully covers what the tool does, when to use it (after generate_workflow), and what it returns (goal, stage, per-step details).

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

Parameters4/5

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

Schema coverage is 100% for the single parameter. The description adds helpful context by specifying the source of workflow_id ('returned by generate_workflow'), linking the tools together.

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?

The description clearly states the tool polls workflow status and lists the return fields (goal, stage, per-step job IDs/statuses). It distinguishes from sibling get_job_status by targeting workflows.

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 description implies polling usage via 'Poll the status' and emphasizes it is for workflows from generate_workflow, but does not explicitly state when not to use it or compare with alternatives like wait_for_job.

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