Skip to main content
Glama

aide_discover

Scan .aide spec files to understand project architecture and intent lineage before reading code, providing progressive disclosure of strategy, research, and implementation context.

Instructions

Scan for .aide spec files in this project. Returns a tree map of where specs live, following progressive disclosure.

Without a path: returns a lightweight project-wide map — file locations and types only, no content. Use this once to understand the project's spec architecture.

With a path: the response opens with the ancestor chain — the cascading intent lineage from project root down to the target directory, with each ancestor showing its description and alignment status (aligned/misaligned when set). The ancestor chain gives you the full inherited context before you read a single spec body. After the ancestor chain comes the detailed subtree of the target directory — summaries extracted from file content and anomaly warnings. Use this to drill into the area you're working on.

.aide files are progressive disclosure specs that live next to orchestrator code — they contain intent (strategy, implementation contracts, anti-patterns), research (sources, data, patterns), or QA checklists (todo). Read .aide files BEFORE reading code — they are the context layer between folder structure and implementation details.

File types (.aide, intent.aide, research.aide, plan.aide, todo.aide):

  • .aide — Intent spec (default). Strategy, contracts, anti-patterns.

  • intent.aide — Same as .aide, used only when research.aide exists in the same folder.

  • research.aide — Raw research. Sources, data points, pattern synthesis.

  • plan.aide -- Architect's implementation plan. Checkboxed steps for the implementor.

  • todo.aide — QA re-alignment document. Captures where implementation drifted from intent.

Never have both .aide and intent.aide in the same folder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoSubdirectory to drill into. When provided, the response opens with the ancestor chain — the cascading intent lineage from root to target, each ancestor showing its description and alignment status — followed by the detailed subtree with summaries and warnings. When omitted, returns a shallow project-wide map (locations and types only).
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does an excellent job explaining the progressive disclosure behavior (lightweight map vs. detailed subtree), the ancestor chain concept, and the different response formats based on the path parameter. It also explains the purpose of .aide files and their types, which helps the agent understand what it's scanning for. The only minor gap is lack of explicit mention of error handling or performance characteristics.

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 appropriately front-loaded with the core purpose, but it contains extensive explanatory material about .aide file types and their purposes that, while helpful for context, could be considered beyond what's strictly necessary for tool selection. The description is comprehensive but somewhat verbose at 12 sentences, with some redundancy in explaining file types.

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

Completeness4/5

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

Given the tool's complexity (progressive disclosure behavior based on parameter), no annotations, and no output schema, the description does an excellent job explaining the behavioral nuances, different use cases, and what to expect in responses. It provides crucial context about .aide files and their types. The only gap is the lack of output format details, but this is somewhat compensated by the behavioral explanation.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds significant value beyond the schema by explaining the semantic difference in behavior: 'Without a path: returns a lightweight project-wide map... With a path: the response opens with the ancestor chain...' This clarifies how the parameter fundamentally changes the tool's behavior and output structure, which goes beyond the schema's technical description.

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?

The description clearly states the tool's purpose: 'Scan for .aide spec files in this project. Returns a tree map of where specs live, following progressive disclosure.' It specifies the verb ('scan'), resource ('.aide spec files'), and distinguishes from siblings by focusing on discovery/mapping rather than reading, initializing, or validating files.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool vs. alternatives: 'Without a path: returns a lightweight project-wide map... Use this once to understand the project's spec architecture. With a path: ... Use this to drill into the area you're working on.' It also distinguishes from sibling tools by explaining this is for scanning/discovery, while others like aide_read are for reading file content.

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/aidemd-mcp/server'

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