Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

get_flow

Read-onlyIdempotent

Retrieve ordered steps, reusable pattern IDs, and recovery considerations for a product journey so you can map, reuse, and troubleshoot the flow.

Instructions

Get ordered steps, reusable pattern IDs and recovery considerations for a product journey.

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": {
      "id": "<id>"
    },
    "name": "get_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description contributes genuine value by disclosing the shape of the payload (ordered steps, pattern IDs, recovery considerations), but says nothing about what happens when the id does not resolve.

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?

A single, front-loaded sentence with no filler; every clause names a distinct part of the return value. Only mild vagueness in 'recovery considerations' keeps it from being maximally informative.

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 one-parameter read tool with no output schema, telling the agent what fields come back is the main missing piece and it is supplied. The remaining gap is the identity format of the required id, which leaves the agent guessing how to construct a valid call.

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

Parameters2/5

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

The single parameter is completely undocumented (0% schema coverage) and the description never mentions 'id' at all — not whether it is a flow ID, slug, or name, nor the 120-character limit contextually. The description does not compensate for the schema gap.

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

Purpose4/5

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

States a specific verb ('Get') and resource ('product journey' / flow) and enumerates what is returned: ordered steps, reusable pattern IDs, recovery considerations. An agent can tell it retrieves a single journey definition rather than a list, though it never explicitly contrasts itself with list_flows.

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

Usage Guidelines3/5

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

Usage is only implied by the verb 'Get' and the singular resource; there is no explicit statement of when to use this instead of list_flows or the reference-guide/design-pack siblings, and no prerequisites or failure conditions are given.

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