Skip to main content
Glama
GethosTheWalrus

Temporal MCP Server

by GethosTheWalrus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

continue_as_new

Signal a running Temporal workflow to restart with new inputs while preserving its history link.

Instructions

Signal a workflow to continue as new (restart with new inputs while preserving history link)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceNoTemporal namespace for this operation; omit to use the server default
signal_argsNoArguments for the signal that will trigger continue-as-new
signal_nameYesThe signal name to send (must be handled by the workflow to trigger continue-as-new)
workflow_idYesThe workflow ID to continue as new

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

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a real behavioral trait – the workflow restarts while preserving a history link – which is valuable. However, it omits permissions, whether the operation is asynchronous, and what happens if the signal is unhandled.

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?

A single front-loaded sentence with the key behavioral clarification in parentheses. Zero filler, and the most important information (what happens to the workflow) comes immediately after the action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A mutation tool with no annotations and no output schema, but with full schema coverage on four parameters. The description explains the effect on the workflow but leaves gaps around authorization, async behavior, and how it relates to the plain signal_workflow sibling.

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 every parameter is already documented in the schema, making 3 the baseline. The description adds only the framing that signal_args are inputs for the triggering signal, which is largely redundant with the schema text.

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 ('signal') and resource ('workflow') and explains the mechanism: restart with new inputs while preserving a history link. This differentiates it from the generic signal_workflow sibling, though it never names that sibling or explicitly contrasts the two.

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 the parenthetical (restart with new inputs), but there is no explicit when-to-use, when-not-to-use, or named alternative among siblings like signal_workflow, terminate_workflow, or cancel_workflow. The agent must infer when continue-as-new is preferable to termination.

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