Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

memory_update

Update a memory while preserving its history: creates a new version and supersedes the old instead of overwriting, keeping prior states traceable.

Instructions

[Wicked Memory] Update without overwriting: creates a new version and closes the old one (valid_until / superseded_by). Omitted fields carry over; only the current version can be updated (409 otherwise).

Use when you want to change a memory while keeping its history (a new version supersedes the old). Not for removing it (use memory_delete).

Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

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

Input Schema

NameRequiredDescriptionDefault
tagsNoReplacement tags.
nonceYesFrom memory_prepare (single use).
sourceNoNew source label.
walletYesYour agent's 0x wallet address.
contentNoNew text (re-embedded). Provide at least one of content/tags/metadata/source.
metadataNoReplacement metadata object.
memory_idYesUUID of the CURRENT version to supersede.
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.7/5.0
Behavior5/5

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

Annotations already flag readOnlyHint=false, non-idempotent and non-destructive; the description goes well past them by disclosing the versioning model, that omitted fields carry over, and that only the current version is updatable (409 otherwise) — a concrete failure mode an agent must anticipate. It also flags the wallet/signature auth requirement, though 'noted above where applicable' is a dangling reference to context not present in this record.

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?

Front-loaded with the key mechanic, then usage, then behavior — three tight blocks with no redundancy. The final sentence's 'noted above where applicable' is filler that points at nothing and could be cut or replaced with the actual auth requirement.

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 9-parameter, non-idempotent write with no output schema, the description covers the semantics that matter: versioning, partial-update behavior, auth, and the 409 failure case. It stops short of saying what the response contains (e.g. the new version's id), which is the main remaining gap.

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 the baseline would be 3, but 'Omitted fields carry over' resolves a real ambiguity created by schema wording like 'Replacement tags' and 'Replacement metadata object' — it tells the agent this is a partial update, not a whitelist replacement. The memory_id wording ('CURRENT version to supersede') is reinforced by the description's 409 rule.

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 plus the non-obvious mechanics: creating a new version and closing the old one via valid_until / superseded_by. It also explicitly contrasts itself with memory_delete, so an agent can separate it from the delete sibling 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?

'Use when you want to change a memory while keeping its history' gives the positive trigger, and 'Not for removing it (use memory_delete)' gives both the exclusion and the named alternative. The 409-only-current-version constraint further bounds when the call will succeed.

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