Skip to main content
Glama
tosin2013

mcp-adr-analysis-server

by tosin2013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

analyze_environment

Read-onlyIdempotent

Assess your project environment against requirements, standards, and ADRs to uncover optimization gaps. Optional memory integration tracks environment snapshots over time for informed decisions.

Instructions

Analyze environment context and provide optimization recommendations with optional memory integration for environment snapshot tracking

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathNoPath to project directory.
adrDirectoryNoDirectory containing ADR filesdocs/adrs
analysisTypeNoType of environment analysis to performcomprehensive
requirementsNoEnvironment requirements (for compliance analysis)
industryStandardsNoIndustry standards to assess compliance against
currentEnvironmentNoCurrent environment specifications (for compliance analysis)
enableTrendAnalysisNoEnable analysis of environment changes over time using stored snapshots
enableMemoryIntegrationNoEnable memory entity storage for environment snapshot tracking and historical analysis

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / properties / enableMemoryIntegration
      Added value: +{
+  "default": true,
+  "description": "Enable memory entity storage for environment snapshot tracking and historical analysis",
+  "type": "boolean"
+}
    • addedInput schema / properties / enableTrendAnalysis
      Added value: +{
+  "default": true,
+  "description": "Enable analysis of environment changes over time using stored snapshots",
+  "type": "boolean"
+}
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The description discloses 'optional memory integration for environment snapshot tracking' and mentions enabling 'memory entity storage', which implies write operations to a memory store. This contradicts the readOnlyHint annotation that indicates no side effects. The contradictory information undermines transparency about the tool's actual behavior.

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 concise sentence that covers the primary purpose and the optional memory feature. It is well-structured and front-loaded with the main action, though it could be slightly more granular without becoming verbose.

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?

The description omits critical context: it does not describe the output format, how recommendations are presented, whether any side effects occur (beyond the memory note), or when to use this tool relative to siblings. Given the read-only annotation and the absence of an output schema, the description leaves significant gaps for an agent deciding how to invoke it.

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?

All eight parameters have descriptions, but they are minimal and mostly restate the parameter names (e.g., 'Path to project directory'). The enum values for analysisType are not explained, and nested objects like 'requirements' lack detail on structure or purpose. The descriptions provide basic help but do not add meaningful semantic depth beyond what the schema already suggests.

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 states a clear verb ('analyze') and object ('environment context'), and specifies an outcome ('provide optimization recommendations'). It also mentions optional memory integration, which differentiates it somewhat from generic analysis. However, it lacks specificity about what 'environment' encompasses and how it differs from similar sibling tools like analyze_project_ecosystem.

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?

No guidance is provided on when to use this tool versus the many sibling analysis tools. The description does not mention alternative tools or conditions that would make this tool preferable. Users must infer usage from the name alone.

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