Skip to main content
Glama
Sign In
DevFlow MCP Server

DevFlow MCP Server

by FaerberK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

project_bootstrap_audit

Audit a codebase to bootstrap project knowledge, generating a structured prompt with subsystem defaults, dedup-list, and instructions for creating architecture pages and knowledge drafts. Re-running skips existing entries.

Instructions

Bootstrap the knowledge base of a project by auditing its code. Returns a structured prompt: default subsystem list (auth/data/api/frontend/realtime/billing/admin/mobile/docs/devops/testing), dedup-list of existing ADRs/drafts/pages, and explicit instructions for Claude to read the local repo with Glob/Grep/Read and then create architecture_module pages + knowledge drafts.

Call this once per new project. Idempotent — re-running will skip existing entries via the dedup-list.

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

Input Schema

NameRequiredDescriptionDefault
projectIdNoProject ID (defaults to linked project).
subsystemsNoOptional custom subsystem list. If omitted, uses auto-detect defaults.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.35.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations, but description discloses idempotent behavior, output contents (subsystem list, dedup-list), and side effects (creating pages/drafts). Could add permissions or error cases.

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?

Concise (~80 words), front-loaded purpose, then output summary, then usage note. No wasted 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?

No output schema, but description fully explains return value (prompt with lists and instructions). Parameters are well-documented. Complete for a bootstrap tool.

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 covers both params; description adds useful default behavior for subsystems field and lists defaults, enhancing schema info.

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 'bootstrap' and resource 'knowledge base of a project', specifying it audits code. Uniquely identifies its function among many sibling tools.

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 says to call once per new project and notes idempotency with dedup-list. Lacks explicit when-not or alternatives, but context makes it clear.

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