Skip to main content
Glama
Sign In
mcp-hyperspace-memory

mcp-hyperspace-memory

Official
by YARlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

memory_forget

Delete a specific memory by numeric memory_id from the agent_cognitive_memories_129 collection, returning success status and a confirmation message.

Instructions

Delete a specific memory by numeric memory_id from collection 'agent_cognitive_memories_129'. Returns a JSON object with success status and confirmation message.

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": {
      "memory_id": "<memory_id>"
    },
    "name": "memory_forget"
  }
}

Input Schema

NameRequiredDescriptionDefault
memory_idYesThe memory ID to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses the return shape (success status and confirmation message), but says nothing about permanence/irreversibility, whether deletion is hard or soft, what happens when the memory_id does not exist, or any required permissions. For a destructive mutation tool with zero annotation coverage, those are significant omissions.

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?

Two tight sentences: the action and its target lead, and the return value follows. Nothing is padded, though the collection name is a long literal that adds little for the calling agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with full schema coverage and no annotations, the essentials (what it deletes, by what key, what it returns) are present. Missing are the destructive-operation semantics an agent needs before committing: irreversibility and behavior on a bad or missing ID.

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 coverage is 100% and the single parameter is already documented as "The memory ID to delete." The description adds only the detail that the ID is numeric and scoped to a named collection; that is marginal value over the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Delete a specific memory") plus the identifier and target collection, which distinguishes it from siblings like memory_remember, memory_recall, and memory_update. It stops short of explicitly naming those siblings as alternatives, but the operation is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to call this versus memory_update or memory_consolidate, and no note that updating a memory may be preferable to deleting it. The agent must infer that this is the destructive path from the verb alone.

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