Skip to main content
Glama
Sign In
DuDuClaw

DuDuClaw

by zhixuli0406
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

memory_store

Save a free-text note to persistent memory; search finds it later and prompts can inject it. Returns a memory ID and never overwrites existing entries.

Instructions

Save one free-text note to your own memory; memory_search finds it and later prompts get it injected. Returns memory_id. Never overwrites. Per-user preferences go to user_profile_record.

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": {
      "content": "<content>"
    },
    "name": "memory_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOptional tags (array, or a comma-separated string); memory_search can filter on them
contentYesThe note, plain text; stored as one entry

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.74.0
    • changedInput schema / properties / content / description
      Previous value: -"Memory content"New value: +"The note, plain text; stored as one entry"
    • changedInput schema / properties / tags / description
      Previous value: -"Comma-separated tags"New value: +"Optional tags (array, or a comma-separated string); memory_search can filter on them"
    • addedInput schema / properties / tags / items
      Added value: +{
+  "type": "string"
+}
    • changedInput schema / properties / tags / type
      Previous value: -"string"New value: +"array"
  2. First observedv1.73.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds real value on top: 'Never overwrites' clarifies the mutation semantics, and 'Returns memory_id' fills in a return value that has no output schema. It doesn't cover anything like rate limits, dedup, or size limits on the note, which leaves a modest gap.

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?

Four short clauses, front-loaded with the action, and each sentence carries distinct information: what it stores, how it's retrieved, what it returns, and where the sibling use case goes. No filler.

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?

For a two-parameter, single-purpose write tool with a fully documented schema and no output schema, the description covers storage semantics, retrieval path, return value, and alternative routing. Nothing an agent needs to call it correctly is missing.

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 both content and tags are already documented in the schema, including the comma-separated-string fallback. The description adds only the framing that content is a single plain-text note; it says nothing about tags. 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?

States a specific verb+resource ('Save one free-text note to your own memory') and pins down scope: one note, one entry, own memory. It explicitly names sibling interactions (memory_search finds it, user_profile_record for preferences), so the agent can distinguish it from neighboring tools without opening schemas.

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 when-to-use and when-not-to-use with named alternatives: use this for free-text notes, and route per-user preferences to user_profile_record instead. It also explains the downstream payoff (memory_search and prompt injection), which tells the agent why to store at all.

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