Skip to main content
Glama
cachly-dev

Cachly — AI Cognitive Brain

index_project

Index local source files into a semantic cache so AI assistants can find relevant files without re-reading the entire codebase each session.

Instructions

Index local source files into the cachly semantic cache so AI assistants can use semantic_search to find relevant files instead of re-reading the whole codebase every time. Walks a directory recursively, reads each matching file, and stores a summary + path as a semantic cache entry (prompt = file path + content excerpt, value = relative path). Requires an embedding provider (OPENAI_API_KEY or CACHLY_EMBED_PROVIDER + key). Run once, then re-run after major refactors. TTL=86400 (24h) keeps entries fresh.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_idYesUUID of the cachly instance
dirYesAbsolute path to the directory to index (e.g. /Users/you/myproject/src)
extensionsNoFile extensions to include (default: ["ts","js","go","py","java","rs","md","kt","swift"])
max_filesNoMaximum number of files to index (default: 100)
ttlNoTTL in seconds for indexed entries (default: 86400 = 24 h)
summary_charsNoCharacters to use as summary per file (default: 1200)
namespaceNoSemantic namespace to store under (default: cachly:sem:code)
Behavior3/5

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

Describes recursive directory walk, file reading, and cache storage. Missing details on side effects like overwriting behavior for re-indexed files, and no mention of null result or error handling. With no annotations, more disclosure would strengthen trust.

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?

Four concise, front-loaded sentences with no fluff. Every sentence adds value: purpose, mechanism, prerequisites, and usage pattern.

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 no output schema and moderate complexity, description adequately covers purpose, prerequisites, and usage. Lacks details on return value, progress indication, or error conditions, but is sufficient for basic understanding.

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?

Input schema descriptions cover all 7 parameters (100% coverage), so description adds minimal extra meaning—only repeats defaults already in schema. Baseline score of 3 is appropriate.

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?

Description clearly states the tool indexes local source files into a semantic cache for AI semantic search, differentiating it from other cache tools and semantic_search sibling.

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?

Provides clear context: requires an embedding provider, run once then after major refactors, and TTL keeps entries fresh. However, lacks explicit when-not-to-use or comparison to alternatives like sync_file_changes for incremental updates.

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/cachly-dev/cachly-mcp'

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