Skip to main content
Glama
GethosTheWalrus

Temporal MCP Server

by GethosTheWalrus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

start_activity

Start a standalone Temporal activity execution by specifying activity type, unique activity ID, and task queue. Use it to run an activity independently without a workflow.

Instructions

Start a new standalone Temporal activity execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoArguments to pass to the activity
activityYesActivity type name to start
namespaceNoTemporal namespace for this operation; omit to use the server default
task_queueYesTask queue for this activity
activity_idYesUnique identifier for the activity execution
start_to_close_timeout_secondsNoActivity start-to-close timeout in seconds

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 supplied, so the description carries the full behavioral burden. It only says it starts an activity; it does not disclose idempotency/duplicate-activity_id behavior, error handling, whether the activity runs detached from any workflow, or what the call returns for a mutation-style operation.

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 zero filler, which is efficient. It is arguably too terse given the tool's complexity, but as pure conciseness it wastes nothing.

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 mutation/execution tool with six parameters, a nested args object, no annotations, and no output schema demands more than one sentence. Key facts an agent needs — whether it is safe to retry, how this differs from execute_activity, and what timeout defaults apply — are absent.

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 six parameters including args, namespace, and the timeout are already documented in the schema. The description adds nothing beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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 and resource ('Start a new standalone Temporal activity execution') and the word 'standalone' hints at a distinction from a workflow-bound execution. However, it never names or contrasts the sibling execute_activity, so an agent cannot be fully sure which of the two activity-starting tools to pick.

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 guidance on when to use this versus execute_activity, start_workflow, or the batch variants. The 'standalone' hint is the only contextual cue and no exclusions or prerequisites are stated.

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