Skip to main content
Glama
dbos-inc

DBOS MCP Server

Official
by dbos-inc

get_schedule

Retrieve detailed configuration and status for a specific schedule in DBOS Conductor by providing application and schedule names, including workflow, cron expression, and last fired time.

Instructions

Get details of a specific schedule from DBOS Conductor.

Args: application_name (string, required): Name of the DBOS application schedule_name (string, required): Name of the schedule

Returns: 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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schedule_nameYes
application_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It discloses return fields and notes that context is omitted for private-mode applications, which is useful. However, it does not mention permissions, error conditions, or whether the tool has no side effects (though 'get' implies read-only).

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 one-sentence purpose followed by Args and Returns sections. It is concise, front-loaded, and every line serves a purpose. The return fields are enumerated clearly without excess verbosity.

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

Completeness4/5

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

Given the tool's simplicity (2 parameters) and the presence of an output schema, the description is largely complete. It covers the tool's function, parameters, and return values. The only gap is the lack of usage guidance relative to sibling tools, which is minor for a getter.

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?

The input schema has no descriptions (0% coverage), and the description provides minimal explanations: 'Name of the DBOS application' and 'Name of the schedule'. This adds some meaning beyond the raw field names but does not offer deeper context such as format, constraints, or typical values.

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 states 'Get details of a specific schedule from DBOS Conductor' with a specific verb ('Get') and resource ('details of a specific schedule'). This clearly distinguishes it from sibling tools like list_schedules (which lists all schedules) and management tools like pause_schedule or 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 clearly implies this tool is for retrieving a single schedule by name, providing context for when it should be used (when you need details of one schedule). However, it does not explicitly mention alternatives or exclusions, such as 'use list_schedules to find schedule names' or 'does not list all schedules.'

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