Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

memory_history

Read-onlyIdempotent

Retrieve a memory's complete version chain, oldest first, including validity windows and superseded-by links from any version ID. Use it to trace history; get current content separately.

Instructions

[Wicked Memory] Full version chain for a memory, oldest first, with valid_from / valid_until / superseded_by. Works from any version's id.

Use when you want a memory's full version chain and validity windows. Not for its current content (use memory_get).

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceYesFrom memory_prepare (single use).
walletYesYour agent's 0x wallet address.
memory_idYesUUID of any version in the chain.
signatureYesYour wallet's signature over memory_prepare's message_to_sign.
timestampYesFrom memory_prepare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond annotations: ordering is oldest first, the chain includes valid_from / valid_until / superseded_by, and any version id can be used as the starting point.

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 short and front-loads the return shape and usage guidance. The final 'Behavior: read-only' sentence repeats what annotations already declare, so it is slightly redundant, but the overall structure remains efficient.

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?

With no output schema, the description does the work of explaining the returned fields and ordering, which is important for this tool. The authentication parameters are covered by the schema, so the definition is nearly complete, though it could mention whether the chain is paginated or always full.

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 every parameter is already documented, including that memory_id is a UUID of any version in the chain. The description reinforces this but does not add meaning beyond what the schema provides.

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 resource and operation: the full version chain for a memory, oldest first, with validity fields. It also distinguishes itself from memory_get by scoping the tool to historical versions rather than current content.

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 states when to use it (full version chain and validity windows) and when not to use it (current content, directing the agent to memory_get). This gives a clear routing decision between siblings.

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