Skip to main content
Glama
Draco-Cheng

ai-readme-manager

by Draco-Cheng

update_ai_readme

Record project decisions and conventions into AI_README.md to keep documentation current and ensure future code follows established patterns.

Instructions

CALL THIS to record DECISIONS and CONVENTIONS.

WHEN TO CALL:

A. CONFLICT RESOLUTION — STOP IMMEDIATELY when any of these occur:

  • User says: "don't use X", "use Y instead", "prefer", "switch to".

  • During planning: user's request or your proposal differs from AI_README conventions.

  • During planning: user approves a plan that contradicts AI_README.

  • User overrides a convention mid-task (even casually, e.g. 'just use X here').

  • DO NOT continue planning or coding. Call update_ai_readme first, then resume.

B. ARCHITECTURAL DECISIONS (during planning/implementation):

  • You chose a design pattern (e.g., repository pattern, factory, singleton).

  • You decided on API structure (REST paths, error format, response shape).

  • You established naming conventions (files, functions, variables).

  • You created new abstractions (utilities, hooks, services, types).

  • You set up error handling strategy or validation approach.

  • You introduced a new dependency or integration pattern.

C. IMPLEMENTATION PATTERNS (after writing code):

  • You created a reusable pattern others should follow.

  • You established a file/folder structure for a new feature.

  • You made decisions that affect future development.

D. MISSING / UNDOCUMENTED (during get_context or code review):

  • AI_README is missing a convention that is ALREADY USED in 2+ existing files.

  • A pattern exists in code but not in AI_README — record it so future code follows it.

  • Do NOT record one-off choices or speculative future patterns.

RULE: If a decision will affect MORE THAN ONE FILE or FUTURE CODE → RECORD IT.

WORKFLOW:

  1. get_context (read current conventions).

  2. Make decision or detect conflict.

  3. update_ai_readme (record the decision).

  4. Continue with implementation.

Content Rules:

  • Extremely concise (default < 400 tokens; project may set a higher tokenBudget).

  • Only actionable conventions (tech, naming, patterns, infrastructure patterns, testing patterns).

  • NO explanations or examples

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationsYesList of update operations to perform
readmePathYesPath to the AI_README.md file to update
projectRootYesProject root directory. Config (.aireadme.config.json) is read from here.
Behavior4/5

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

With no annotations, the description carries the burden and it largely delivers: it frames the call as a recording action that should happen before continuing work, and specifies content constraints and the 'last resort' treatment of rewrites. It does not explicitly state that the tool mutates the file on disk or what the return/error behavior is, but the schema's operation details and the tool name make the mutation obvious.

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 long, but it is front-loaded with the core purpose and organized into scannable sections and lettered categories. Every section earns its place; it is verbose only because the tool's trigger conditions are complex and high-stakes.

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

Completeness5/5

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

For a complex decision-recording tool with no annotations and no output schema, the description combined with the detailed input schema is sufficient: it covers triggering conditions, the required preceding get_context step, what to record, what not to record, and how to format content. An agent can determine both when to invoke the tool and how to invoke it correctly.

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?

Schema coverage is 100%, so the baseline is 3; the description adds value by adding a default token budget (<400 tokens), requiring actionable conventions only, and prohibiting explanations/examples, which directly shapes the operations.content parameter. It does not re-explain readmePath/projectRoot, but those are fully documented in the schema.

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 opening line, 'CALL THIS to record DECISIONS and CONVENTIONS', states a specific action and resource, and the tool name reinforces it. It is clearly distinguished from siblings like init_ai_readme, compress_ai_readme, and get_context_for_file, which create, shrink, or read the file rather than record decisions.

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 gives exhaustive when-to-call criteria across conflict resolution, architectural decisions, implementation patterns, and undocumented conventions, plus explicit exclusions ('Do NOT record one-off choices or speculative future patterns') and a rule threshold ('affects MORE THAN ONE FILE or FUTURE CODE'). It also embeds a workflow that orders get_context before update_ai_readme and says to continue after recording.

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