Skip to main content
Glama
Sign In
DevFlow MCP Server

DevFlow MCP Server

by FaerberK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

doc_page_list

List all documentation pages grouped by section, showing titles and IDs, to review existing docs before adding or updating content.

Instructions

List all documentation pages for a project, grouped by section. Returns sections with their pages (title, id, section, sortOrder). Use this to see what documentation exists before creating or updating pages.

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": "doc_page_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.6/5.0
Behavior4/5

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

With no annotations provided, the description carries full responsibility. It discloses that the tool is read-only (listing pages) and describes the return format. It could explicitly state no side effects, but the word 'list' implies safety. The automatic project linking is a useful behavioral detail.

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?

The description is compact with three to four sentences. It front-loads the core purpose and then adds return details and usage advice. Efficient, though could potentially combine the last two sentences.

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?

All relevant aspects are covered: what the tool does, what it returns, when to use it, and how to call it (with optional projectId). No output schema exists, but the description sufficiently conveys the return structure. No gaps.

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?

Schema coverage is 100% with a clear description for projectId. The description adds value by restating the automatic linking behavior in natural language, which reinforces understanding. This goes beyond the schema's baseline.

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 'List all documentation pages for a project, grouped by section' and specifies the return structure (title, id, section, sortOrder). It uses a specific verb and resource, and distinguishes itself from sibling tools like doc_page_create or doc_page_update.

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?

Explicitly advises to use this tool 'before creating or updating pages', giving a concrete use case. It also explains the automatic project linking behavior when projectId is omitted, providing clear context for usage.

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