Skip to main content
Glama

bootstrap_project

Reads project documentation files to populate memory hot cache, enabling quick context for new codebases.

Instructions

Bootstrap hot cache from project documentation files.

Scans for common project documentation files (README.md, CLAUDE.md, etc.), parses them into memories, and optionally promotes to hot cache.

This is ideal for quickly populating the hot cache when starting work on a new codebase.

Edge cases handled gracefully:

  • Empty repo: Returns success with files_found=0 and helpful message

  • No markdown files: Returns success with message

  • File read errors: Logged in errors list, continues with other files

  • Empty files: Skipped silently

  • Binary files: Skipped with warning

  • All content already exists: Returns memories_skipped count

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags to apply to all memories
root_pathNoProject root directory (default: current directory).
memory_typeNoMemory type for all contentproject
file_patternsNoSpecific files to seed. If not provided, auto-detects: CLAUDE.md, README.md, CONTRIBUTING.md, ARCHITECTURE.md
promote_to_hotNoPromote all bootstrapped memories to hot cache

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorsNo
messageNo
successYes
files_foundNo
files_processedNo
memories_createdNo
memories_skippedNo
hot_cache_promotedNo
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses read-like behavior (scans, parses) and details edge cases (empty repo, no markdown, file read errors, binary files). Could be more explicit about non-modification of files, but overall strong.

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?

Concise and well-structured with a clear main sentence followed by bullet points of edge cases. Every sentence adds value, with no redundancy.

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?

Given the presence of an output schema and full parameter descriptions, the description is complete. It covers purpose, usage context, and edge cases, leaving no significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds context: explains default file patterns, root_path, and the role of tags. This goes beyond the schema descriptions, enhancing understanding.

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: bootstrapping the hot cache from project documentation files. It specifies actions like scanning, parsing, and promoting, and the verb 'Bootstrap' is specific. It distinguishes from sibling tools like seed_from_file or warm_cache by focusing on batch processing of common documentation files.

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?

Explicitly mentions ideal use case: 'when starting work on a new codebase.' However, it does not explicitly state when not to use it or compare with alternatives, which is a minor gap.

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/michael-denyer/memory-mcp'

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