Skip to main content
Glama
GethosTheWalrus

Temporal MCP Server

by GethosTheWalrus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

start_workflow

Launch a new Temporal workflow execution by specifying its name, unique ID, task queue, and optional JSON arguments and namespace.

Instructions

Start a new Temporal workflow execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoArguments to pass to the workflow (as JSON object)
namespaceNoTemporal namespace for this operation; omit to use the server default
task_queueYesThe task queue to use for this workflow
workflow_idYesUnique identifier for the workflow execution
workflow_nameYesThe name of the workflow to start

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. 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, yet it only says 'Start a new'. It says nothing about idempotency, what happens on workflow_id collision, whether the call blocks until completion, or what the execution returns. For a workflow-launching mutation with no annotation coverage, this is a substantial gap.

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?

A single front-loaded sentence with no wasted words. It is concise and well-structured, though its brevity leaves much unsaid rather than being over-padded.

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 five-parameter mutation tool with a nested 'args' object, no output schema, and no annotations, the description is too thin. It omits return/run semantics, execution blocking behavior, failure modes, and any usage context an agent would need to call it correctly.

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, including the nested 'args' JSON object and the namespace default. The description adds no parameter-level detail beyond the schema, making the baseline 3 appropriate.

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 (start) and resource (Temporal workflow execution), so an agent can distinguish it from query_workflow, signal_workflow, cancel_workflow, etc. It does not explicitly name sibling alternatives, but the operation is unambiguous.

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 when-to-use guidance, prerequisites, or alternatives are given. The description does not explain when to use start_workflow versus start_activity/execute_activity, or what conditions must be met (e.g., a running Temporal server, namespace setup).

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