Skip to main content
Glama
Sign In
muninn-local-mcp

muninn-local-mcp

by wolfcao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_delete

Delete a specific memory from your project by providing its ID. Removes outdated or incorrect memories to keep your project's memory accurate.

Instructions

Delete a specific memory from the current project by its ID.

Args: memory_id: The full or partial ID of the memory to delete (required).

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

Input Schema

NameRequiredDescriptionDefault
memory_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the deletion action, but does not mention irreversibility, confirmation steps, cascading effects, or any other behavioral traits. This is minimal transparency for a destructive operation.

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 extremely concise: two sentences, the first stating the purpose and the second explaining the argument. No unnecessary words, front-loaded with the core action.

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 simple one-parameter deletion tool, the description covers the basic purpose and parameter meaning. However, it does not mention the output schema (which exists) or any error conditions, leaving some context gaps.

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?

The input schema has 0% description coverage; the description adds the nuance that memory_id can be a full or partial ID, which is not in the schema. However, it does not explain the format or how to obtain a memory ID. This partially compensates but lacks completeness.

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 clearly states the action (delete), the resource (memory), and the scope (from the current project by its ID). This effectively distinguishes it from sibling tools that list, search, or write memories, including global variants.

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?

The description does not provide any guidance on when to use this tool versus alternatives. It mentions 'current project' but does not contrast with global memory tools, and offers no conditions, prerequisites, or exclusions.

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