Skip to main content
Glama
GethosTheWalrus

Temporal MCP Server

by GethosTheWalrus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

batch_cancel_activities

Cancel multiple standalone Temporal activities matching a query, with concurrent processing to handle batches faster. Set concurrency to control parallel operations (default 50).

Instructions

Cancel multiple standalone activities matching a query with concurrent processing for speed. Use 'concurrency' to control parallel operations (default: 50).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of activities to cancel (default: 100)
queryYesQuery to select activities to cancel
namespaceNoTemporal namespace for this operation; omit to use the server default
concurrencyNoNumber of activities to cancel 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 exist, so the description carries the full behavioral burden. It discloses the parallelism approach and default concurrency, but says nothing about irreversibility, what happens to partially matched or already-completed activities, failure handling, or what a cancellation actually does to a running activity.

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 tight sentences with the core action front-loaded and the concurrency tip second. No wasted words, though the parenthetical default duplicates the schema.

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?

For a destructive bulk mutation with no annotations and no output schema, the definition leaves key gaps: whether cancellation is graceful or forced, partial-failure reporting, and the shape of any result. An agent cannot confidently predict outcomes from this alone.

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 all four parameters are already documented, including the concurrency default. The description restates the concurrency default rather than adding new semantics (e.g. query syntax or limit interaction), so the 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 (cancel) and resource scope (multiple standalone activities matching a query), and adds the concurrency mechanism. It implicitly distinguishes from cancel_activity (single) and batch_terminate_activities (terminate vs cancel), but never names those siblings explicitly.

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 choose this over cancel_activity, batch_cancel, or batch_terminate_activities, and no preconditions stated. The description only implies bulk use via 'multiple ... matching a query'.

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