Skip to main content
Glama
Sign In
lightbulb-mcp

lightbulb-mcp

by RPasquale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

dynamic_workflow_status

Read-only

Read the current status of a dynamic workflow run using a role-bound continuation receipt, ensuring only authorized roles can access the progress.

Instructions

Read bounded run status with a role-bound continuation receipt.

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": {
      "company_ref": "<company_ref>",
      "project_ref": "<project_ref>",
      "run_ref": "<run_ref>",
      "host_binding_ref": "<host_binding_ref>",
      "session_receipt": "<session_receipt>",
      "host_role": "<host_role>"
    },
    "name": "dynamic_workflow_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_refYes
host_roleYes
company_refYes
project_refYes
session_receiptYes
host_binding_refYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

C2.7/5.0
Behavior3/5

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

The description is consistent with the readOnlyHint annotation and adds some context: the read is 'bounded', and it requires a role-bound continuation receipt, suggesting auth/state constraints. However, it does not explain what happens to the continuation receipt, whether the status is consumed, or what 'bounded' means in practice.

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 description is a single concise sentence with no filler, and the action ('Read') is front-loaded. It is appropriately terse, though the terseness contributes to ambiguity about the key concepts.

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

Completeness2/5

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

With six required parameters, no schema descriptions, and a cryptic one-line description, the tool is under-specified. The presence of an output schema helps with return values, but the description still fails to explain 'bounded run', 'role-bound continuation receipt', or how this tool fits into the dynamic_workflow_* family. An agent would struggle to select and call it correctly.

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?

Schema coverage is 0%, so the description must compensate for six undocumented required parameters. It hints that host_role and session_receipt form the 'role-bound continuation receipt' and that the refs identify a bounded run, but it leaves company_ref, project_ref, run_ref, and host_binding_ref semantically vague. This is insufficient for reliable invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb ('Read') and a resource ('run status'), so the core operation is identifiable. However, the qualifiers 'bounded' and 'role-bound continuation receipt' are jargon-heavy and do not clearly distinguish this from other status/read tools like get_workflow_run or get_recursive_agent_execution_status.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, no lifecycle context (e.g., after dynamic_workflow_start or dynamic_workflow_attach), and no exclusions. The phrase 'bounded run status' implies a specific context, but the description leaves the agent to infer when this is applicable.

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