memcurve

Overview Schema Source Related Servers Discussions Admin

search_memory

Retrieve stored memories by text query, tags, status, recency, and score, with paginated results. Use semantic search and review-due filtering to surface relevant or due memories.

Instructions

Search memories with filters and pagination.

Args: query: Search text (max 50k chars). tags: Filter by tags (max 50). status: Filter by status ('active', 'promoted', 'archived' or list of these). Defaults to ['active', 'promoted'] if None. top_k: Max results (1-100). window_days: Recent memories only (1-3650 days). min_score: Min decay score (0.0-1.0). use_embeddings: Enable semantic search. include_review_candidates: Include review-due memories. page: Page number (default: 1). page_size: Results per page (10-100, default: 10). preview_length: Content chars (0-5000, default: 300).

Returns: Dict with results list and pagination metadata.

Raises: ValueError: Invalid parameters.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`tags`	No
`query`	No
`top_k`	No
`status`	No
`min_score`	No
`page_size`	No
`window_days`	No
`preview_length`	No
`use_embeddings`	No
`include_review_candidates`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Sep 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses important behavior: default status filtering, pagination metadata, supported parameter ranges, ValueError on invalid parameters, and semantic search via use_embeddings. It does not explicitly state read-only semantics, but the 'search' verb makes that reasonably clear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well structured with clear Args, Returns, and Raises sections, and the one-line purpose is front-loaded. It is somewhat long due to 11 parameters, but each line carries useful constraint information rather than padding.

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 an 11-parameter tool with no annotations, the description covers parameter semantics, defaults, return shape, and error behavior, which is sufficient for invoking the tool correctly. The main gap is the lack of guidance on when to choose this tool over sibling search tools, but that is more of a usage-guidance issue.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the Args section compensates fully by explaining every parameter with constraints and defaults, including max query length, tag count, status allowed values, top_k range, and preview_length range. This is exactly the added meaning the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line 'Search memories with filters and pagination' uses a specific verb and resource, making the core purpose clear. However, it does not differentiate itself from sibling tools like search_unified or open_memories, so the agent is left to infer which search tool fits.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description documents filters and pagination but provides no guidance on when to use this tool versus alternatives. There is no mention of search_unified, open_memories, or any condition that would select one search entry point over another.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server