Skip to main content
Glama

Recall similar past work

recall_similar_work
Read-only

Rank past memory notes by similarity to a visual goal, enabling reuse of prior recipes, parameters, and prompts to avoid rebuilding from scratch.

Instructions

Read-only vault search: rank past memory notes by similarity to a new visual goal so the agent can reuse prior recipes, params, and prompts instead of rebuilding from scratch. Scores by query-token overlap with title/intent/prompt/tags/body, with optional tag and op boosts. Returns ranked hits with vault paths, score, matched terms, and an optional body snippet. Offline; requires TDMCP_VAULT_PATH.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opsNoOptional operator types you expect to use (e.g. audioAnalysisCHOP). Boosts notes whose 'ops' overlap.
tagsNoOptional tags that should boost matching notes (additive). Lowercased before match.
limitNoMaximum number of hits to return after sorting.
queryYesFree-text goal/prompt to compare past memory notes against.
min_scoreNoDrop hits whose normalised score is below this threshold.
include_body_snippetNoWhen true, return a ~240-char body excerpt around the best-matching line.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsYes
queryYesEcho of the input query (post-trim).
scannedYesNumber of memory notes considered.
warningsYesPer-note read problems; search continues on error.
vault_pathYesAbsolute path of the configured vault root.
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds 'Read-only vault search' and 'Offline; requires TDMCP_VAULT_PATH', providing additional behavioral context beyond annotations. No contradiction.

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 two sentences, front-loaded with the primary purpose. Every sentence adds value with no wasted words. Highly concise and well-structured.

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 the tool's complexity (6 parameters, output schema exists), the description covers key aspects: purpose, search mechanism, return fields, and requirements. It could mention sorting order explicitly, but it is largely complete.

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 coverage is 100% with all parameters described. The description adds meaning by explaining how the query is used ('Scores by query-token overlap with title/intent/prompt/tags/body') and the role of tags and ops boosts, 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's purpose: 'Read-only vault search: rank past memory notes by similarity to a new visual goal so the agent can reuse prior recipes, params, and prompts instead of rebuilding from scratch.' This is a specific verb+resource and distinguishes from sibling tools that involve creation, analysis, or other operations.

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?

The description provides clear context on when to use the tool (to recall past work for reuse) and constraints ('Offline; requires TDMCP_VAULT_PATH'). It does not explicitly state when not to use or offer alternatives, but the purpose is well-defined.

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/Pantani/tdmcp'

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