Skip to main content
Glama
dbos-inc

DBOS MCP Server

Official
by dbos-inc

get_workflow

Retrieve status, inputs, outputs, errors, and metadata for a specific workflow using its application name and workflow ID. Diagnose issues and track progress.

Instructions

Get details of a specific workflow from DBOS Conductor.

Args: application_name (string, required): Name of the DBOS application workflow_id (string, required): ID of the workflow to retrieve

Returns: workflowId (string): The workflow ID status (string): PENDING, SUCCESS, ERROR, CANCELLED, ENQUEUED, DELAYED, or MAX_RECOVERY_ATTEMPTS_EXCEEDED workflowName (string): The name of the workflow function workflowClass (string, optional): The name of the workflow's class, if any workflowConfig (string, optional): The name with which the workflow's class instance was configured, if any user (string, optional): The user who ran the workflow, if specified assumedRole (string, optional): The role with which the workflow ran, if specified roles (string, optional): All roles which the authenticated user could assume (JSON array) input (string, optional): The workflow input, in a human-readable representation output (string, optional): The workflow's output, if any, in a human-readable representation error (string, optional): The error the workflow threw, if any createdAt (string): Workflow start time (ISO 8601) updatedAt (string): Last time the workflow status was updated (ISO 8601) queueName (string, optional): If this workflow was enqueued, on which queue appVersion (string): The application version on which this workflow was started executorId (string, optional): The executor to most recently execute this workflow timeoutMs (int, optional): The start-to-close timeout of the workflow in ms deadline (string, optional): The deadline of the workflow, computed by adding its timeout to its start time (ISO 8601) deduplicationId (string, optional): Unique ID for deduplication on a queue priority (int): Priority of the workflow on the queue (1-2147483647, lower is higher priority) queuePartitionKey (string, optional): If this workflow is enqueued on a partitioned queue, its partition key forkedFrom (string, optional): If this workflow was forked from another, that workflow's ID parentWorkflowId (string, optional): If this is a child workflow, the ID of the parent workflow that started it dequeuedAt (string, optional): When this workflow was dequeued from its queue (ISO 8601) wasForkedFrom (bool): Whether another workflow has been forked from this one (true on the fork's source, not on the fork itself; a fork has forkedFrom set instead) delayUntil (string, optional): If this workflow has a delayed start, the time until which it is delayed (ISO 8601) completedAt (string, optional): When this workflow completed (ISO 8601) attributes (string, optional): Application-defined attributes attached to the workflow, if any scheduleName (string, optional): If this workflow was started by a schedule, that schedule's name applicationName (string, optional): Name of the application that owns the workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYes
application_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

A3.8/5.0
Behavior3/5

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

Without annotations, the description relies on the word 'Get' to convey a read-only operation, but it does not explicitly state side-effect-free behavior or authorization needs. It compensates with detailed return fields but omits edge-case behavior such as what happens if the workflow ID does not exist.

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 one-sentence purpose is front-loaded, followed by clearly labeled Args and Returns sections. The return list is long, but each field includes explanatory semantics that would not be in a bare output schema, so it earns its place.

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?

For a single-workflow read, the description covers both parameters and all return fields with human-readable meanings. It is slightly incomplete in that it does not describe error handling or not-found behavior, but these are minor for a simple getter.

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%, and the description fully compensates by describing each parameter: 'Name of the DBOS application' and 'ID of the workflow to retrieve.' It also clarifies which are required.

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?

States a specific verb and resource: 'Get details of a specific workflow from DBOS Conductor.' This clearly differentiates from siblings like list_workflows, which return multiple workflows, and cancel_workflow, which mutates.

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 explicit guidance on when to use this tool vs alternatives. While the phrase 'specific workflow' implies an ID lookup, it does not mention list_workflows for listing or state when not to use it. The agent is left to infer usage from context.

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

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