Skip to main content
Glama
GethosTheWalrus

Temporal MCP Server

by GethosTheWalrus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

batch_terminate_activities

Terminate multiple standalone activities matching a query to stop unwanted executions in batch. Control batch size with a limit and set a reason for the termination.

Instructions

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

Input Schema

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

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 burden. It mentions a batch size limit and default but does not disclose destructive nature, irreversibility, permission requirements, effect on running activities, or what happens to activities that don't match the query. This is a significant gap for a termination 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 a useful default. No wasted words, though it could be slightly more informative without becoming verbose.

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?

Given this is a destructive batch operation with no annotations and no output schema, the description is incomplete. It should state that termination is irreversible, whether it affects running activities, and any prerequisite permissions. The current text leaves an agent uncertain about the consequences of calling 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 all parameters. The description adds a default for 'limit' (100) and mentions batch size control, but it does not explain 'reason', 'concurrency', or 'namespace' beyond what is in the schema. Baseline 3 is appropriate when schema is comprehensive.

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?

The description states a specific verb ('Terminate') and resource ('multiple standalone activities') and clarifies batch scope, distinguishing it from terminate_activity and batch_terminate_workflows by naming 'standalone activities'. It is clear but lacks explicit sibling routing.

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?

It gives no guidance on when to use this batch tool versus terminate_activity (singular), batch_cancel_activities, or batch_terminate. The reader must infer that this is for bulk operations, but there is no explicit when-to-use or exclusion criteria.

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