Skip to main content
Glama
Sign In
DevFlow MCP Server

DevFlow MCP Server

by FaerberK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

adr_list

List architecture decision records for a project with optional status filtering. Retrieve ADR numbers, titles, statuses, and decision dates.

Instructions

List all Architecture Decision Records for a project. Optional status filter (proposed | accepted | deprecated | superseded). Returns ADR-###, title, status, decided_at.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adr_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by status
projectIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.35.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, but description discloses behavior: lists records and returns specific fields. No hidden behavior implied, adequate for a simple list tool.

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?

Two sentences, front-loaded with main purpose, no wasted words. Efficiently conveys all necessary information.

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?

Covers purpose, parameters, and return format. Lacks pagination or sorting details, but sufficient for a typical list operation without output schema.

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?

Description adds allowed status values (proposed, accepted, deprecated, superseded) beyond schema, which only says 'Filter by status'. ProjectId is implied by 'for a project', compensating for 50% schema coverage.

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?

Clearly states verb (List), resource (Architecture Decision Records), and scope (for a project). Includes optional filter and return fields, distinguishing it from siblings like adr_get.

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?

Provides clear context for use (listing all ADRs) but does not explicitly mention when not to use or alternatives. However, the purpose is sufficiently distinct.

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

Deploy Server

Other Tools