Skip to main content
Glama
GethosTheWalrus

Temporal MCP Server

by GethosTheWalrus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_schedule

Create a new schedule for periodic workflow execution. Provide the schedule ID, workflow name, task queue, and cron expression to automate recurring runs.

Instructions

Create a new schedule for periodic workflow execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoArguments for the workflow
cronYesCron expression (e.g., '0 12 * * *')
namespaceNoTemporal namespace for this operation; omit to use the server default
task_queueYesTask queue for the workflow
schedule_idYesUnique identifier for the schedule
workflow_nameYesName of the workflow to schedule

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-disclosure burden. It implies a mutation that creates persistent state but omits permissions/auth requirements, duplicate schedule behavior, namespace defaults, return semantics, and whether the schedule starts immediately or must be triggered.

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?

A single front-loaded sentence with no filler. The core action and resource appear immediately, and every word contributes to the stated purpose.

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 6-parameter mutation tool with no annotations and no output schema, one sentence is insufficient. The schema documents fields, but the description omits behavioral context such as duplicate-schedule handling, required permissions, namespace/default behavior, and cron semantics.

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%, and every property has a schema-level description. The tool description adds no parameter-level meaning beyond what the schema already provides, 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?

States a specific verb and resource: 'Create a new schedule for periodic workflow execution.' The purpose is clear, but it does not explicitly differentiate this create operation from sibling schedule tools such as trigger_schedule, pause_schedule, or list_schedules.

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?

Provides no when-to-use or when-not-to-use guidance, no prerequisites, and no alternatives. The agent is left to infer that this should be used instead of trigger_schedule or unpause_schedule when a new recurring schedule is needed.

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