Skip to main content
Glama
Sign In
DevFlow MCP Server

DevFlow MCP Server

by FaerberK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

release_list

List project releases with status, target dates, and descriptions. Automatically uses the linked project when no project ID is provided.

Instructions

List all releases for a project. Returns releases with their status, target dates, and descriptions. Automatically uses the linked project if no projectId is provided.

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": "release_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdNoThe project ID. If omitted, uses the linked project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.35.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the return content and the automatic project association behavior, which is useful context for an agent.

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 concise sentences with the key action front-loaded. No wasted words; every sentence provides relevant information.

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?

For a simple list tool, the description covers what it does, what it returns, and the default project behavior. Without an output schema, it adequately describes the return fields.

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 description essentially restates the schema's parameter description about default behavior, adding no new information beyond the schema.

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 all releases for a project, specifying the return fields and distinguishing it from siblings like release_create, release_get, and release_update.

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?

It provides guidance on automatically using the linked project when no projectId is provided, but does not explicitly state when to use alternatives like release_get for individual releases.

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