Skip to main content
Glama

Get Workflow Details

sirv_get_workflow
Read-onlyIdempotent

Retrieve a saved workflow by ID to inspect its name, description, and each step's type and settings; use it to understand workflow logic or copy step settings into the matching tool.

Instructions

Get one saved workflow by its id in workflow_id: its name, description and every step with its type and settings.

Use it to see what a workflow does, or to copy a step's settings into that step's own tool. MCP cannot run a workflow: it runs in Studio. Find the id with sirv_list_workflows.

Read-only.

Credits: free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workflow_id": "<workflow_id>"
    },
    "name": "sirv_get_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflow_idYesWorkflow id, from sirv_list_workflows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / workflow_id / description
      Previous value: -"ID of the workflow to retrieve"New value: +"Workflow id, from sirv_list_workflows"
    • addedInput schema / properties / workflow_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the 'Read-only.' line is largely redundant. The description does add genuinely new behavioral context: workflows cannot be executed via MCP, and the call is free of credit cost.

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?

Front-loaded with the core action and return shape, then usage, then constraints. Tight overall, though 'Read-only.' duplicates the annotation and could be dropped.

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?

No output schema exists, but the description compensates by describing exactly what is returned (name, description, steps with type and settings), and it covers the execution limitation and cost, leaving nothing an agent needs to call it correctly.

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 coverage is 100% and the schema already documents workflow_id as a UUID sourced from sirv_list_workflows, so the description's mention of the id adds no meaning beyond the structured field. Baseline 3 applies.

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 one saved workflow by its id') and enumerates the returned payload (name, description, every step with type and settings), which cleanly separates it from sirv_list_workflows.

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

Usage Guidelines5/5

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

Gives explicit use cases ('see what a workflow does, or copy a step's settings into that step's own tool'), an explicit exclusion ('MCP cannot run a workflow: it runs in Studio'), and routes the agent to sirv_list_workflows to obtain the id.

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