Skip to main content
Glama

mcp_engram_query_with_momentum

Retrieve concepts that are actively changing or evolving by blending semantic similarity with conceptual trajectory, ideal for tracking trends or shifts in a topic.

Instructions

Momentum-assisted recall: blends semantic similarity (q tensor, 80%) with conceptual trajectory (p tensor, 20%). WHEN TO USE INSTEAD OF recall: When you want to find concepts that are actively changing or evolving, not just ones that statically match your query right now. Example: use this when asking 'what has been changing in the auth system?' because momentum detects blocks whose p tensor is accelerating toward your query topic. Use regular recall when you want stable, crystallized knowledge. Supports zedos_filter (incl. 'training' for Phase 2 NREM-biased richer CLS blocks).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kNoNumber of results to return (default: 5, max: 20)
queryYesNatural language query
zedos_filterNoOptional: filter by memory type (same values as mcp_engram_recall, including 'training' for ZEDOS_TRAINING / richer CLS blocks). Leave unset for all types.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains the tensor blending and the filter for 'training' blocks, but does not explicitly state whether the tool is read-only or has side effects. The behavioral disclosure is partial.

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 very concise: two sentences plus a usage guidance block. The main purpose is front-loaded, and every sentence adds value without 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?

For a query tool with 3 parameters and no output schema, the description covers purpose, usage guidance, parameter hints, and internal mechanism. However, it does not describe the return format or pagination details. A minor gap, but overall complete.

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 coverage is 100% with descriptions for each parameter. The description adds extra context for the zedos_filter parameter (e.g., 'training' value) but does not significantly enhance meaning beyond the schema. Baseline 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?

The description clearly states that the tool performs momentum-assisted recall blending semantic similarity with conceptual trajectory, and explicitly distinguishes it from the sibling 'recall' tool by explaining that it is for evolving concepts.

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 includes an explicit 'WHEN TO USE INSTEAD OF recall' section with an example query, and advises using regular recall for stable knowledge. This provides clear guidance on tool selection.

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/staticroostermedia-arch/engram'

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