Skip to main content
Glama

init_ai_readme

Scans project directories for missing or empty AI_README files, creates root-level guide if absent, and prompts you to document conventions for each path.

Instructions

Initialize and populate empty AI_README files within a project. When to use:

  • First-time setup when no AI_README exists.

  • get_context_for_file reports empty or missing AI_README files.

  • Newly created directories need conventions recorded.

  • Multiple directories require conventions in one pass. What it does:

  • Scans for missing or empty AI_README documents.

  • Creates a root-level AI_README if none is present.

  • Provides directory-specific prompts to gather conventions.

  • Guides you through documenting tech stack, patterns, and naming. Workflow:

  • Call init_ai_readme.

  • Follow the step-by-step instructions to inspect each directory.

  • Use update_ai_readme to record the conventions.

  • Run validate_ai_readmes to check for problems.

  • Fix any warnings (remove redundant content, add Cross-directory dependencies section).

  • Re-run get_context_for_file to confirm coverage before coding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetPathNoSpecific directory to initialize (optional, defaults to scanning entire project)
projectRootYesThe root directory of the project. Use the current working directory (e.g., from environment or pwd). If unsure, pass the project root path.
excludePatternsNoGlob patterns to exclude when scanning
Behavior4/5

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

No annotations provided, so description carries burden. Discloses scanning, creation of root AI_README, and guidance prompts. Could mention idempotency or behavior if AI_README already exists, but overall transparent.

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

Conciseness5/5

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

Description is well-organized with sections, front-loaded with purpose, and every sentence adds value. No fluff.

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?

No output schema, but description and workflow provide a clear picture of the multi-step process. Covers prerequisites, steps, and downstream tools. Lacks details on return format but sufficient for agent.

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% (all three parameters described). Description does not add significant detail beyond the schema for targetPath or excludePatterns. Baseline 3 applies.

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 initializes and populates empty AI_README files, with specific verb and resource. It distinguishes from siblings like update_ai_readme by focusing on first-time setup.

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

Usage Guidelines4/5

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

Explicit 'When to use' section lists four scenarios (first-time setup, empty reports, new directories, multiple directories). Workflow indicates sequence after other tools. Does not explicitly exclude cases, but the guidance is strong.

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/Draco-Cheng/ai-readme-mcp'

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