Skip to main content
Glama
cachly-dev

cachly — AI Cognitive Brain

index_project

Index local source files into a semantic cache, enabling AI assistants to retrieve relevant code without re-reading the whole codebase. Walks directories and stores file summaries with paths.

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)
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses walking directories, reading files, storing summary+path, TTL, and required environment variables. Missing details on error handling or blocking behavior, but adequate.

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?

The description is concise (4 sentences), front-loaded with purpose, then mechanics, prerequisites, and usage cadence. Every sentence adds essential information with no redundancy.

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 7 parameters and no output schema, the description covers purpose, behavior, prerequisites, TTL, and usage frequency. It lacks details on return value or error states, but is mostly complete for agent decision-making.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining defaults, the purpose of TTL, and the effect of parameters on storage, enhancing understanding beyond 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 description clearly states the tool indexes local source files into a semantic cache for AI assistants to use semantic_search, which is a specific verb+resource and distinguishes it from sibling tools like semantic_search.

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?

It provides context on when to use (run once, re-run after major refactors) and prerequisites (embedding provider), but does not explicitly exclude alternative tools or specify when not to use.

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