Wicked MCP server

memory_get

Read-onlyIdempotent

Fetch a stored memory's content by its UUID when you already have the memory ID; use it for direct retrieval, not semantic search.

Instructions

[Wicked Memory] Fetch one of your memories by id (another wallet's or a deleted id returns the same 404).

Use when you have a memory id and want its content. Not for searching by meaning (use memory_search).

Behavior: read-only.

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": {
      "wallet": "<wallet>",
      "memory_id": "<memory_id>",
      "timestamp": "<timestamp>",
      "nonce": "<nonce>",
      "signature": "<signature>"
    },
    "name": "memory_get"
  }
}

Input Schema

Name	Required	Description
`nonce`	Yes	From memory_prepare (single use).
`wallet`	Yes	Your agent's 0x wallet address.
`memory_id`	Yes	The memory's UUID.
`signature`	Yes	Your wallet's signature over memory_prepare's message_to_sign.
`timestamp`	Yes	From memory_prepare.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Oct 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful non-obvious behavior: another wallet's memory or a deleted id returns the same 404. It repeats 'read-only' but does not contradict annotations.

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 short, front-loaded with the core action, and structured into purpose, usage guidance, and behavior. Every sentence contributes to selecting or understanding the tool.

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?

The tool is simple and the annotations plus schema are rich, while the description adds the important 404 behavior and sibling routing. Since there is no output schema, it could say more about the returned memory shape, but overall it is adequately complete for calling the tool correctly.

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 all five parameters are already documented in the schema, including memory_id, wallet, nonce, timestamp, and signature. The description mentions the memory id conceptually but adds no parameter-level syntax or constraints beyond the schema.

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 states a specific verb and resource: 'Fetch one of your memories by id.' It also distinguishes this tool from memory_search by clarifying that it is not for semantic search.

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?

It gives an explicit usage condition ('when you have a memory id and want its content') and an explicit alternative ('Not for searching by meaning (use memory_search)'). No inference is needed to choose between memory_get and memory_search.

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

Deploy Server