Skip to main content
Glama
GethosTheWalrus

Temporal MCP Server

by GethosTheWalrus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_activities

Retrieve standalone activity executions by query in a Temporal namespace, using limit and skip to paginate results.

Instructions

List standalone activity executions based on a query. Specify 'limit' to control results and 'skip' for pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of results to skip for pagination (default: 0)
limitNoMaximum number of results to return (default: 100)
queryNoList filter query (e.g., 'TaskQueue = "my-task-queue"')
namespaceNoTemporal namespace for this operation; omit to use the server default

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 provided, so the description carries the full behavioral burden. 'List' implies a read, but the description never confirms non-mutation, says nothing about permissions, defaults behavior, or what the returned executions look like, and never explains what makes an execution 'standalone'.

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 short sentences that front-load the purpose before the parameter notes, with no filler. Slightly redundant given the schema already documents limit and skip, which keeps it from a 5.

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?

There is no output schema and no annotations, so the description should ideally describe the shape of returned executions and confirm the read-only nature. It stops at purpose plus pagination, leaving an agent to guess the return format and how 'standalone' is determined.

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 in the schema with defaults and an example query. The description restates limit and skip without adding format, syntax, or constraint detail beyond that baseline.

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 ('List standalone activity executions'), and the word 'standalone' usefully distinguishes this from activity executions tied to a workflow. It does not name or contrast with the closest siblings (count_activities, list_workflows), so an agent must infer the boundary itself.

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?

The description explains how to control results with limit/skip, which is pagination mechanics rather than usage guidance. It gives no when-to-use condition, no exclusions, and no pointer to count_activities or other listing tools when the agent only needs a total.

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