mcp-adr-analysis-server

get_development_guidance

Translate architectural decisions into specific coding tasks and implementation patterns for your development phase, technology stack, and team context.

Instructions

Get comprehensive development guidance that translates architectural decisions and workflow recommendations into specific coding tasks, implementation patterns, and development roadmap

Input Schema

TableJSON Schema

Name	Required	Description
`developmentPhase`	Yes	Current development phase
`adrsToImplement`	No	List of ADR titles or file paths that need to be implemented in code
`technologyStack`	No	Current technology stack (e.g., ["TypeScript", "React", "Node.js", "PostgreSQL", "Docker"])
`currentProgress`	No	What has already been implemented or current state of development
`teamContext`	No
`timeline`	No	Development timeline or deadline constraints
`focusAreas`	No	Specific areas to focus on (e.g., ["API design", "database schema", "testing strategy", "deployment pipeline"])

Implementation Reference

src/types/tool-arguments.ts:36-47 (schema)

TypeScript interface defining the input arguments (GetDevelopmentGuidanceArgs) for the get_development_guidance MCP tool.

export interface GetDevelopmentGuidanceArgs {
  developmentPhase?: string;
  adrsToImplement?: string[];
  technologyStack?: string[];
  currentProgress?: string;
  teamContext?: {
    size?: string;
    experienceLevel?: string;
  };
  timeline?: string;
  focusAreas?: string[];
}

src/tools/tool-catalog.ts:1196-1215 (registration)

Central registration of the get_development_guidance tool in TOOL_CATALOG Map. Defines metadata, category ('workflow'), input schema, token cost, related tools, and CE-MCP support for dynamic MCP tool discovery and listing.

TOOL_CATALOG.set('get_development_guidance', {
  name: 'get_development_guidance',
  shortDescription: 'Get development guidance',
  fullDescription: 'Provides development guidance and best practices.',
  category: 'workflow',
  complexity: 'moderate',
  tokenCost: { min: 1500, max: 3000 },
  hasCEMCPDirective: true, // Phase 4.3: Moderate tool - development guidance
  relatedTools: ['get_workflow_guidance', 'mcp_planning'],
  keywords: ['development', 'guidance', 'best-practices'],
  requiresAI: true,
  inputSchema: {
    type: 'object',
    properties: {
      topic: { type: 'string' },
      level: { type: 'string', enum: ['beginner', 'intermediate', 'advanced'] },
    },
    required: ['topic'],
  },
});

src/utils/server-context-generator.ts:304-305 (helper)
Tool name and description listed in server context generator's hardcoded tool list for documentation and categorization in .mcp-server-context.md.
```
name: 'get_development_guidance',
description: 'Get development guidance and best practices',
```

Tool Definition Quality

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While it mentions the tool provides 'comprehensive development guidance,' it doesn't describe what form this guidance takes (e.g., structured output, natural language, step-by-step tasks), whether it's generative or retrieval-based, or any limitations like response length, processing time, or context window constraints. For a complex guidance tool with no annotation coverage, this represents a significant gap in behavioral transparency.

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 a single, well-constructed sentence that efficiently communicates the tool's purpose and transformation process. It's appropriately sized for the tool's complexity, though it could potentially be more front-loaded with the core functionality before detailing the translation process.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex guidance-generation tool with 7 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the output looks like (critical since there's no output schema), doesn't mention any prerequisites or limitations, and doesn't provide examples of typical use cases. The high parameter count and absence of structured output information make this description incomplete for effective tool selection and invocation.

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?

With 86% schema description coverage, the input schema already documents most parameters well. The description adds no specific parameter semantics beyond what's in the schema - it doesn't explain how parameters like 'adrsToImplement' or 'technologyStack' influence the guidance generation, nor does it provide examples of effective parameter combinations. The baseline 3 is appropriate when the schema does most of the documentation work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get comprehensive development guidance that translates architectural decisions and workflow recommendations into specific coding tasks, implementation patterns, and development roadmap.' It specifies the verb ('Get'), resource ('development guidance'), and transformation process, though it doesn't explicitly differentiate from sibling tools like 'get_workflow_guidance' or 'generate_deployment_guidance' which might have overlapping domains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools in related domains (e.g., 'get_workflow_guidance', 'generate_deployment_guidance', 'troubleshoot_guided_workflow'), there's no indication of when this specific guidance tool is appropriate or what distinguishes it from other guidance-generating tools in the server.

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

Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security
Open Source Has a Bot Problem
By punkpeye on March 19, 2026.
open source

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/tosin2013/mcp-adr-analysis-server'

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