Skip to main content
Glama
cloin

SemaphoreUI MCP Server

by cloin

update_schedule

Modify an existing schedule's settings including template, cron expression, schedule type, and active status within a project.

Instructions

Update an existing schedule.

Args: project_id: ID of the project schedule_id: ID of the schedule to update template_id: ID of the template to run name: Schedule name cron_format: Cron expression for recurring schedules active: Whether the schedule is enabled schedule_type: Schedule type: "" for cron, or "run_at" for one-time runs run_at: RFC3339 timestamp for one-time schedules task_params: Optional task parameters to pass when the schedule runs delete_after_run: Delete the one-time schedule after it runs repository_id: Optional repository ID for commit-check schedules

Returns: Updated schedule details or empty dict on success

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
schedule_idYes
template_idNo
nameNo
cron_formatNo
activeNo
schedule_typeNo
run_atNo
task_paramsNo
delete_after_runNo
repository_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but only says 'Update an existing schedule.' No details on side effects, authorization, error handling, or guarantees are given.

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?

The description is well-structured as a docstring with Args and Returns sections. It is appropriately detailed for 11 parameters, with no extraneous content; every line serves a purpose.

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?

The description covers parameter semantics adequately but lacks behavioral context such as error cases, idempotency, or prerequisites. The presence of an output schema partially compensates, but overall completeness is moderately sufficient.

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?

Each parameter has a brief semantic description (e.g., 'schedule_type: Schedule type: "" for cron, or "run_at" for one-time runs'). This adds meaning beyond the schema, though depth is limited and no examples or constraints are provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'Update an existing schedule,' a clear verb+resource pairing. It distinguishes this tool from siblings like create_schedule and delete_schedule, which handle other lifecycles.

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 provided on when to use this tool versus alternatives. It does not mention prerequisites, when not to use, or conditions for invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cloin/semaphore-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server