Skip to main content
Glama
GethosTheWalrus

Temporal MCP Server

by GethosTheWalrus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

execute_activity

Runs a standalone Temporal activity on a specified task queue and waits for its result, letting you execute activity logic directly by type and arguments.

Instructions

Execute a standalone Temporal activity and wait for result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoArguments to pass to the activity
activityYesActivity type name to execute
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?

With no annotations, the description carries the full burden of behavioral disclosure. It does mention the blocking behavior of waiting for a result, which is useful, but omits critical traits such as authorization requirements, timeout semantics, error handling, and whether the activity execution is idempotent or creates new state. Much remains undisclosed.

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?

The description is a single, front-loaded sentence with no wasted words. It efficiently conveys the core action and the key behavioral hint of waiting for a result.

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 tool with six parameters, no output schema, and no annotations, the description is too thin. It does not explain return value format, error or timeout behavior, or how the result is delivered, leaving significant gaps that an agent would need to call it correctly in non-trivial cases.

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 six parameters thoroughly. The description adds no additional parameter meaning, so the baseline of 3 is 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?

The description states a specific verb ('Execute') and resource ('standalone Temporal activity') and adds the scope behavior 'wait for result'. However, it does not differentiate itself from the sibling tools start_activity or get_activity_result, leaving the agent to infer the distinction from the name alone.

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 is given about when to use this tool versus alternatives like start_activity or get_activity_result. The words 'standalone' and 'wait for result' imply a synchronous use case but fall short of 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