Skip to main content
Glama
Sign In
DuDuClaw

DuDuClaw

by zhixuli0406
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

memory_search

Read-only

Search stored notes and chat-learned facts by keyword or tags to find relevant memories before answering from recall; returns results and total as JSON.

Instructions

Keyword search over your own memory: notes you stored plus facts the gateway learned from your chats. Returns JSON {results,total}. Use before answering from recall; for a known id use memory_read.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "memory_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOnly entries carrying at least one of these tags (array, or a comma-separated string)
limitNoMax results (default 10, max 100)
queryYesKeywords or a short phrase to match

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.74.0
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max results (default 10, max 100)",
+  "type": "integer"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Search query"New value: +"Keywords or a short phrase to match"
    • addedInput schema / properties / tags
      Added value: +{
+  "description": "Only entries carrying at least one of these tags (array, or a comma-separated string)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observedv1.73.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered. The description adds the search modality (keyword, not semantic), the corpus being searched, and the return shape {results,total}, which is meaningful since no output schema exists. It stops short of describing pagination or how the limit interacts with total.

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?

Three short clauses, front-loaded with the action and scope, then the return contract, then the disambiguation. No filler sentences.

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 low-complexity, fully documented 3-param read tool with no output schema, the description supplies the missing return shape and the routing rule. Only the result-count/limit behavior is left implicit in the schema.

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%, so query, tags, and limit are all documented in the schema with formats and defaults. The description only reinforces that matching is keyword-based; it adds no syntax or filtering detail beyond that, so the baseline 3 applies.

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?

Specific verb+resource (keyword search over memory) plus an explicit scope statement: notes stored by the user and facts learned from chats. It also distinguishes itself from the closest sibling by naming memory_read for the known-id case.

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?

Gives both a when-to-use trigger ("before answering from recall") and an explicit alternative with its selecting condition ("for a known id use memory_read"). An agent can route between the two without opening either schema.

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

Deploy Server

Other Tools