Skip to main content
Glama

List SDLC pipeline phases

list_sdlc_phases
Read-onlyIdempotent

Retrieve the ordered list of agentic-sdlc pipeline phases with their skip conditions and human judgment gates to understand the workflow sequence and decision points.

Instructions

List the agentic-sdlc pipeline phases in execution order, with each phase's skip condition and the judgment gates it raises — the points where the flow must stop for a human decision. Use it to drive the SDLC flow yourself in a host that cannot run the plugin, or to answer what happens when in the pipeline. Returns the phase and gate skeleton only; read source_uri for what each phase actually does. Takes no arguments. Read-only and idempotent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
phasesYesEvery pipeline phase, in execution order from phase 0.
source_uriYesURI of the pipeline skill this map was parsed from. Read it with get_document for what each phase actually does — this tool returns only the phase/gate skeleton.
Behavior4/5

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

Annotations already provide readOnlyHint and idempotentHint. Description adds that it returns a skeleton, phases are from source_uri, and it's read-only and idempotent, adding context beyond annotations.

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?

Three sentences, front-loaded with purpose, usage, and return details. Every sentence adds value without redundancy.

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?

Complete for a zero-parameter, read-only tool with annotations. Output schema exists, so return values are covered. Description adds usage context and clarification about the skeleton vs source_uri.

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

Parameters4/5

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

No parameters in schema (baseline 4). Description adds no parameter info, but none needed.

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 lists SDLC pipeline phases in execution order with skip conditions and judgment gates, using specific verb and resource. It distinguishes from sibling tools like search_methodology or list_presets.

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?

Explicitly mentions use cases: driving SDLC flow in hosts that cannot run the plugin or answering pipeline questions. No explicit exclusions, but context is clear.

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/Jarroslav/agentic-os'

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