Skip to main content
Glama

analyze_project_ecosystem

Recursively analyze a project's ecosystem to reveal its architecture, dependencies, technologies, and environment. Leverages advanced prompting with knowledge generation and reflexion learning for insightful, context-aware analysis.

Instructions

Comprehensive recursive project ecosystem analysis with advanced prompting techniques (Knowledge Generation + Reflexion)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathNoPath to the project directory to analyze (optional, uses configured PROJECT_PATH if not provided)
includePatternsNoFile patterns to include in analysis
enhancedModeNoEnable advanced prompting features (Knowledge Generation + Reflexion)
knowledgeEnhancementNoEnable Knowledge Generation for technology-specific insights
learningEnabledNoEnable Reflexion learning from past analysis outcomes
technologyFocusNoSpecific technologies to focus analysis on (auto-detected if not provided)
analysisDepthNoDepth of ecosystem analysiscomprehensive
includeEnvironmentNoAutomatically include comprehensive environment analysis (default: true)
recursiveDepthNoDepth of recursive project analysiscomprehensive
analysisScopeNoSpecific analysis areas to focus on (e.g., ["security", "performance", "architecture", "dependencies"])
conversationContextNoRich context from the calling LLM about user goals and discussion history
Behavior2/5

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

The description mentions 'Knowledge Generation + Reflexion' but does not explain what these entail, side effects, permissions, or output format. With no annotations, the description fails to disclose behavioral traits beyond the name and generic 'analysis'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but packed with jargon ('Knowledge Generation + Reflexion'). It lacks structure and could be clearer, though it does front-load the core purpose. Every word earns its place, but clarity suffers.

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?

Given the complexity (11 parameters, nested objects, no output schema), the description is incomplete. It does not explain return values, how advanced features work, or practical usage patterns, leaving the agent to rely solely on parameter descriptions.

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?

Schema coverage is 100% with detailed parameter descriptions, so the schema already provides parameter semantics. The tool description adds no additional meaning beyond the brief mention of advanced techniques, earning the baseline score of 3.

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 performs 'comprehensive recursive project ecosystem analysis' with advanced prompting techniques. It identifies the resource (project ecosystem) and the action (analysis), but lacks explicit differentiation from sibling tools like 'analyze_environment', making it less precise in distinguishing its scope.

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 alternatives. Sibling tools include simpler analyses (e.g., analyze_environment) and specific analyses (e.g., analyze_gaps), but the description does not specify contexts where this comprehensive tool is preferable or when to avoid it.

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