Skip to main content
Glama
GethosTheWalrus

Temporal MCP Server

by GethosTheWalrus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

batch_terminate

Terminate multiple Temporal workflows matching a query to stop many executions at once. Set an optional limit to control batch size and provide a reason.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of workflows to terminate (default: 100)
queryYesQuery to select workflows to terminate
reasonNoReason for termination
namespaceNoTemporal namespace for this operation; omit to use the server default

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

C2.9/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. For a bulk, forced-termination operation it omits critical context: that termination is destructive and irreversible, whether it skips graceful cleanup, permission requirements, and what happens to workflows already in flight. Only the default batch size is disclosed, and that is already in the schema.

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 action, no padding. Slight deduction because the second sentence restates a default already present in the schema rather than adding new information.

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 four-parameter destructive batch tool with no annotations and no output schema needs more than this description: it never says what termination does to the target workflows, whether the operation is partial/resumable, or how many matched versus terminated. The agent has no safety or outcome context.

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 baseline is 3 and the schema already documents query, reason, namespace, and limit. The description's mention of 'limit' merely restates the schema default (100) rather than adding query syntax or reason semantics.

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?

Specific verb and resource: 'Terminate multiple workflows matching a query.' The batch semantics are clear and distinguish it from the singular terminate_workflow, but nothing separates it from the sibling batch_cancel, which implies a different (graceful vs forced) operation.

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?

No statement of when to use batch_terminate versus batch_cancel, terminate_workflow, or batch_terminate_activities. The only guidance is a schema-duplicating note about 'limit', with no exclusions or context about when a batch termination is appropriate.

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