Skip to main content
Glama
tosin2013

mcp-adr-analysis-server

by tosin2013
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

get_workflow_guidance

Receive tailored workflow guidance and tool recommendations to document architectural decisions based on your project goals and current context.

Instructions

Get intelligent workflow guidance and tool recommendations based on your goals and project context to achieve expected outcomes efficiently

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYesWhat you want to accomplish (e.g., "analyze new project", "document existing decisions", "security audit", "modernize legacy system")
projectContextYesCurrent state of your project (e.g., "new project", "existing project with ADRs", "legacy codebase", "greenfield development")
availableAssetsNoWhat assets you already have (e.g., ["PRD.md", "existing ADRs", "codebase", "documentation", "test suite"])
timeframeNoAvailable time/effort level
primaryConcernsNoMain areas of concern (e.g., ["security", "performance", "maintainability", "scalability", "compliance"])

Implementation Reference

  • src/types/tool-arguments.ts:7-13 (schema)
    Type definition for tool input arguments (schema)
    export interface GetWorkflowGuidanceArgs {
  goal: string;
  projectContext: string;
  availableAssets?: string[];
  timeframe?: string;
  primaryConcerns?: string[];
}
  • src/tools/tool-catalog.ts:1175-1194 (registration)
    Tool metadata registration in central catalog used for dynamic MCP tool listing and discovery
    TOOL_CATALOG.set('get_workflow_guidance', {
  name: 'get_workflow_guidance',
  shortDescription: 'Get workflow guidance',
  fullDescription: 'Provides guidance for specific workflows.',
  category: 'workflow',
  complexity: 'moderate',
  tokenCost: { min: 1500, max: 3000 },
  hasCEMCPDirective: true, // Phase 4.3: Moderate tool - workflow guidance
  relatedTools: ['get_development_guidance', 'mcp_planning'],
  keywords: ['workflow', 'guidance', 'help', 'process'],
  requiresAI: true,
  inputSchema: {
    type: 'object',
    properties: {
      workflowType: { type: 'string' },
      context: { type: 'string' },
    },
    required: ['workflowType'],
  },
});
  • src/utils/server-context-generator.ts:300-302 (registration)
    Tool listed in server context documentation (informational)
      name: 'get_workflow_guidance',
  description: 'Get workflow guidance for specific development tasks',
},

Tool Definition Quality

B3.2/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 the full burden of behavioral disclosure. While it mentions the tool provides 'guidance and recommendations,' it doesn't clarify whether this is a read-only operation, what format the output takes, whether it's resource-intensive, or if there are any rate limits. For a tool with 5 parameters and no annotation coverage, this is a significant gap in 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-structured sentence that efficiently communicates the core purpose without unnecessary words. It's front-loaded with the main action and context. However, it could be slightly more concise by removing 'to achieve expected outcomes efficiently,' which is somewhat redundant with 'guidance.'

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

Completeness3/5

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

Given the tool's complexity (5 parameters, no annotations, no output schema), the description is minimally adequate. It states what the tool does but lacks details on behavioral traits, output format, or error handling. Without annotations or an output schema, the agent has insufficient information to fully understand how to interpret results or potential limitations.

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?

The schema description coverage is 100%, with all parameters well-documented in the input schema itself. The description adds no additional parameter semantics beyond what's already in the schema (e.g., it doesn't explain how parameters interact or provide examples of combined usage). This meets the baseline of 3 when the schema does the heavy lifting, but no extra value is added.

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 intelligent workflow guidance and tool recommendations based on your goals and project context to achieve expected outcomes efficiently.' It specifies the verb ('Get'), resource ('workflow guidance and tool recommendations'), and context ('based on your goals and project context'). However, it doesn't explicitly differentiate this from sibling tools like 'get_development_guidance' or 'troubleshoot_guided_workflow', which prevents a perfect score.

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

Usage Guidelines3/5

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

The description implies usage context ('based on your goals and project context') and suggests this is for achieving outcomes 'efficiently,' but it doesn't provide explicit guidance on when to use this tool versus alternatives like 'get_development_guidance' or 'troubleshoot_guided_workflow.' No exclusions or prerequisites are mentioned, leaving the agent to infer appropriate usage scenarios.

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

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