Skip to main content
Glama
marerem

longmem

search_similar

Retrieve cached solutions from cross-project memory by describing your current problem. Check if a known solution already exists before building a new one.

Instructions

Search the cross-project memory for solutions similar to the current problem.

Call this FIRST before reasoning about a problem from scratch. If similarity ≥ threshold a cached solution is returned — check edge_cases to see if any known limitations apply to the current context. If no match is found, solve normally and then call confirm_solution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
problemYesDescribe the problem you are trying to solve.
categoryNoProblem domain. One of: ci_cd, containers, infrastructure, cloud, networking, observability, auth_security, data_pipeline, ml_training, model_serving, experiment_tracking, llm_rag, llm_api, vector_db, agents, database, api, async_concurrency, dependencies, performance, testing, architecture, other. Use 'other' when unsure.other
tagsNoOptional keywords to narrow the search — library names, framework, error type, tool name. E.g. ['kubernetes','oom','python'].
languageNoProgramming language if relevant, e.g. 'python', 'typescript'.
thresholdNoMinimum similarity (0–1). Defaults to similarity_threshold in config.toml (default 0.85).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes the core behavior: returns cached solution if threshold met, and mentions checking edge_cases for limitations. No annotations exist, so the description adequately covers the expected workflow and side-effect-free nature.

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?

Extremely concise: one sentence for purpose, two sentences for usage guidance. Every sentence adds distinct 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 output schema exists and the description integrates with siblings (edge_cases, confirm_solution), it provides a complete picture for an agent to use the tool correctly in a multi-step workflow.

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?

Schema description coverage is 100%, so the baseline is 3. The description does not add significant value beyond the schema's parameter explanations, but it provides useful context about when and how to use the tool.

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 searches cross-project memory for similar solutions. It distinguishes from siblings like search_by_project and list_recent by specifying 'cross-project' and positioning it as the first step.

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?

Explicitly instructs to call this tool before reasoning from scratch, and provides conditional logic for threshold matches and edge-case checks, referencing sibling tool confirm_solution.

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/marerem/longmem'

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