Skip to main content
Glama
zhixuli0406

DuDuClaw

by zhixuli0406
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

memory_fetch_batch

Read-only

Fetch up to 100 memory entries by ID in a single call instead of repeated reads. Returns found memories plus any unknown IDs in missing_ids, so batches never fail.

Instructions

Fetch up to 100 of your memory entries by id in one call. Returns {memories, missing_ids}; unknown or foreign ids go to missing_ids instead of failing. Use instead of repeated memory_read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesMemory entry ids (UUIDs), 1 to 100
include_metadataNoAlso return tags, layer and created_at (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.74.0
    • changedInput schema / properties / ids / description
      Previous value: -"Array of memory entry UUIDs to fetch (max 100)"New value: +"Memory entry ids (UUIDs), 1 to 100"
    • addedInput schema / properties / ids / items
      Added value: +{
+  "type": "string"
+}
    • changedInput schema / properties / ids / type
      Previous value: -"string"New value: +"array"
    • changedInput schema / properties / include_metadata / description
      Previous value: -"Include full metadata (tags, layer, created_at). Default false"New value: +"Also return tags, layer and created_at (default false)"
    • changedInput schema / properties / include_metadata / type
      Previous value: -"string"New value: +"boolean"
  2. First observedv1.73.3

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint/openWorldHint, and the description adds genuinely new behavior: the return shape {memories, missing_ids} and the partial-failure tolerance that unknown or foreign ids land in missing_ids rather than aborting the call. That is exactly the kind of non-obvious error semantics an agent needs. It stops short of covering ordering or permission expectations, so a 4 rather than 5.

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 sentences, zero filler, and the batch scope plus return/error contract are front-loaded before the routing advice. Every clause earns its place.

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?

With no output schema present, the description carries the return-value burden and does so: it names both response fields and the failure mode. Nothing an agent needs to invoke this two-parameter read tool correctly is missing.

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%, so both parameters are already documented, giving a baseline of 3. The description adds meaning beyond the schema by tying the '1 to 100' cap and the unknown/foreign-id behavior to how ids are interpreted, which helps the agent construct a safe batch call.

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 and resource ('Fetch ... memory entries by id'), gives the batch cap (up to 100), and names the sibling it replaces ('Use instead of repeated memory_read'), so an agent can distinguish it from memory_read/memory_search without opening any schema.

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?

Explicitly routes the agent: use this instead of repeated memory_read when fetching many entries by id. The single-read alternative and the condition that selects the batch form are both stated, leaving nothing to inference.

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