Skip to main content
Glama

Signal, query, or update a running workflow

workflow_interact

Interact with running workflow executions by sending signals, running queries, or applying updates to manage workflow state.

Instructions

Send a signal to or run a query against a running workflow execution.

action=signal: fire-and-forget event; the workflow reacts asynchronously.

  • name: signal name defined in the workflow.

  • input: optional payload matching the signal's schema.

action=query: synchronous read of internal workflow state.

  • name: query handler name defined in the workflow.

  • input: optional parameters for the query.

  • Returns query_name + result inline.

action=update: synchronous request to modify workflow state mid-execution.

  • name: update handler name defined in the workflow.

  • input: optional payload for the update.

  • Returns update_name + result inline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesInteraction type.
executionIdYesTarget execution ID.
nameYesSignal or query handler name.
inputNoOptional payload for the signal or query.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
execution_idYes
messageNoConfirmation message for signal actions.
query_nameNo
update_nameNo
resultNoQuery or update result payload.
Behavior5/5

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

Annotations provide only basic hints (readOnlyHint=false, etc.), but the description adds critical behavioral details: signal is fire-and-forget, query returns inline results, update modifies state synchronously. No contradictions with annotations.

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?

Description is well-structured with a concise overview followed by bullet points for each action. Every sentence adds value, no repetition or fluff. Front-loaded with the core purpose.

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?

Covers all three action types and their effects. Mentions return values for query and update. Could mention that the workflow must be running, but overall sufficiently complete for the tool's complexity.

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

Parameters5/5

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

Input schema has 100% description coverage, but the description adds context per action: explains how 'name' and 'input' are used differently for signal, query, and update, and notes that query/update return results inline. This goes beyond the schema.

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?

Description clearly states the tool sends signals, queries, or updates a running workflow execution. It distinguishes three actions (signal, query, update) with specific verbs and the resource (running workflow), setting it apart from siblings like workflow_execute and workflow_status.

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?

Description explains when to use each action (e.g., signal is fire-and-forget, query is synchronous read). It does not explicitly state when not to use the tool or compare with alternatives, but the action-specific guidance provides clear usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Swih/mistral-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server