Skip to main content
Glama
dbos-inc

DBOS MCP Server

Official
by dbos-inc

list_schedules

List cron-based schedules for a DBOS application and filter them by status, workflow name, or name prefix to manage automated workflow triggers.

Instructions

List schedules for an application from DBOS Conductor.

Schedules automatically trigger workflows on a cron-based schedule.

Args: application_name (string, required): Name of the DBOS application status (string or array of strings, optional): Filter by schedule status (e.g., "ACTIVE", "PAUSED") workflow_name (string or array of strings, optional): Filter by the workflow function the schedule triggers schedule_name_prefix (string or array of strings, optional): Filter by schedule name prefix

Returns: schedules: Array of schedule objects, each containing: - schedule_id (string): Unique identifier - schedule_name (string): Name of the schedule - workflow_name (string): The workflow function this schedule triggers - workflow_class_name (string, optional): The workflow's class name, if any - schedule (string): Cron expression defining the schedule - status (string): "ACTIVE" or "PAUSED" - context (string, optional): Schedule context (JSON string; omitted for private-mode applications) - last_fired_at (string, optional): When the schedule last triggered (ISO 8601) - automatic_backfill (bool): Whether missed runs are automatically backfilled - cron_timezone (string, optional): Timezone for the cron expression count (int): Number of schedules returned application (string): Name of the application queried

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo
workflow_nameNo
application_nameYes
schedule_name_prefixNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

There are no annotations provided, so the description carries the full burden. It gives detailed return behavior but does not explicitly state that the operation is read-only or mention any auth requirements, rate limits, or side effects. The read-only nature is implied but not stated.

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 well-structured with a clear summary, Args section, and Returns section. It is appropriately sized for the tool's complexity, with no filler or redundant information, and the purpose is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete for a listing tool: it covers the purpose, all parameters, and the full return structure. It also provides context about what schedules are. No critical information is missing for correct invocation and interpretation of results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does so effectively by explaining all four parameters, including types, optionality, and examples (e.g., status can be 'ACTIVE' or 'PAUSED'). This adds significant meaning beyond the bare input schema.

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 clearly states the tool's purpose: 'List schedules for an application from DBOS Conductor.' It uses a specific verb and resource, and the additional context about schedules triggering workflows distinguishes it from sibling tools like get_schedule, pause_schedule, and trigger_schedule.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool (to list schedules for an application) but does not explicitly mention alternatives or exclusions. The context is sufficient for an agent to infer appropriate use, but there is no direct comparison to sibling tools like get_schedule.

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/dbos-inc/dbos-mcp'

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