Skip to main content
Glama
cachly-dev

cachly — AI Cognitive Brain

semantic_search

Find cached entries semantically similar to a natural-language query. Returns matching keys, values, and similarity scores.

Instructions

Find cached entries that are semantically similar to a natural-language query. Read-only — no side effects. Returns an array of objects, each with: key, value, similarity_score (0–1), and namespace. Returns an empty array if no entries meet the similarity threshold. Requires OPENAI_API_KEY (or compatible provider) and the Speed/Business tier with CACHLY_VECTOR_URL. Embeddings are computed server-side and never leave Germany (pgvector HNSW index). Example: "find all cached responses about password reset" or "what did we answer about pricing?". Use cache_get for exact key lookup; use smart_recall for brain lessons.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_idYesUUID of the cache instance (from list_instances)
queryYesNatural-language query to find similar cached content
thresholdNoMinimum cosine similarity 0–1 (default: 0.82). Lower = broader matches.
namespaceNoSemantic namespace to search in (default: cachly:sem)
top_kNoMaximum number of results to return (default: 5)
use_hybridNoEnable Hybrid BM25+Vector RRF fusion search. Passes `hybrid: true` and the query text to the pgvector API for higher precision on named entities. Default: false.
auto_namespaceNoAuto-detect the namespace from the query text using text heuristics instead of using the `namespace` parameter. Returns results only from the matching domain (code/translation/summary/qa/creative).
Behavior5/5

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

The description declares the tool is read-only with no side effects, explains server-side embedding computation and privacy (data never leaves Germany), and describes return shape including empty array behavior. This is comprehensive given no annotations.

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 but thorough, front-loading the purpose, then covering behavior, requirements, privacy, examples, and alternatives in a logical order. Every sentence adds value.

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 complexity (7 parameters, hybrid search, auto_namespace) and lack of output schema, the description covers all necessary aspects for an agent: purpose, behavior, return format, requirements, privacy, and alternatives. No gaps.

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?

The input schema already has 100% description coverage for all 7 parameters, so the description adds little beyond the schema. It provides example usage and explains hybrid search, but these are minor additions.

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 finds cached entries semantically similar to a natural-language query. It distinguishes from siblings by explicitly naming cache_get and smart_recall as alternatives.

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 provides explicit guidance on when to use this tool (semantic search) and when to use alternatives (cache_get for exact lookup, smart_recall for brain lessons). It also notes prerequisites like OPENAI_API_KEY and Speed/Business tier.

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