Skip to main content
Glama
GethosTheWalrus

Temporal MCP Server

by GethosTheWalrus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_workflows

Retrieve Temporal workflow executions by query, with limit and skip controls for pagination. Use it to inspect or monitor workflows matching specific filters.

Instructions

List workflow executions based on a query. Specify 'limit' to control the number of results (default: 100, max recommended: 1000). Use 'skip' to paginate through results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of results to skip for pagination (default: 0)
limitNoMaximum number of results to return (default: 100, increase for more results)
queryNoList filter query (e.g., 'WorkflowType="MyWorkflow"')
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. 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. It hints at result-count control but does not state that this is a read-only listing, whether pagination is cursor- or offset-based across calls, or what the response contains. For a tool with zero annotation coverage this is a notable 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?

Two tightly written sentences with the purpose front-loaded and pagination guidance following. No filler, though the phrasing is slightly cramped.

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?

With four parameters, no annotations, and no output schema, the description leaves the return shape and read-only nature unexplained and offers no routing among the many sibling listing and query tools. It is adequate for pagination defaults but incomplete for correct invocation in this crowded toolset.

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 four parameters and the baseline is 3. The description adds one genuinely new detail, the max recommended limit of 1000, but says nothing about the query filter syntax or the namespace parameter beyond what the schema provides.

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 workflow executions') that distinguishes it from siblings like list_activities and list_schedules. The qualifier 'based on a query' is vague but the core object of 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?

The description explains how to use limit and skip but never says when this tool should be chosen over alternatives such as query_workflow or get_workflow_history. No prerequisites, context, or exclusions are given, leaving tool selection to inference.

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