Skip to main content
Glama
GethosTheWalrus

Temporal MCP Server

batch_signal

Send a signal to multiple Temporal workflows matching a query, with an optional limit to control batch size.

Instructions

Send a signal to multiple workflows matching a query. Specify 'limit' to control batch size (default: 100).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoArguments for the signal
limitNoMaximum number of workflows to signal (default: 100)
queryYesQuery to select workflows
namespaceNoTemporal namespace for this operation; omit to use the server default
signal_nameYesThe signal name to send

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.1
    • addedInput schema / properties / namespace
      Added value: +{
      +  "description": "Temporal namespace for this operation; omit to use the server default",
      +  "enum": [
      +    "default"
      +  ],
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Addedv1.9.0
  3. Removedv1.5.0
  4. First observedv1.3.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says signals are sent to a batch but not what happens on partial failure, whether the call is idempotent, what permissions are needed, or whether the signal is fire-and-forget or blocking — all material for a batch mutation tool.

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?

Two short sentences, front-loaded with the core action and followed by the one parameter nuance worth surfacing. No filler, though the second sentence only echoes a schema default.

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?

A five-parameter batch mutation tool with a nested args object, no annotations, and no output schema. The description does not address partial-batch outcomes, error behavior, or the args payload shape, leaving significant gaps for an agent deciding how to call and interpret it.

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 the schema already documents query, signal_name, args, limit, and namespace. The description only restates the limit default, adding no semantics beyond the schema; baseline 3 applies.

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?

States a specific verb and resource: 'Send a signal to multiple workflows matching a query.' The 'multiple workflows matching a query' phrasing distinguishes it in spirit from the sibling signal_workflow (singular), though it never names that sibling explicitly.

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?

Usage is implied by 'matching a query' and the batch/multi-workflow framing, but there is no explicit when-to-use guidance, no exclusions, and no mention of the single-target signal_workflow alternative for non-batch cases.

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