Skip to main content
Glama
Sign In
mem-universe

mem-universe

by H1an1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete

Delete a memory file from the shared git-backed store. Removed files are recoverable through version history, ensuring safe removal.

Instructions

Delete a memory file. Git keeps history, so it's recoverable. Returns {ok, deleted}.

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": {
      "path": "<path>",
      "author_agent": "<author_agent>"
    },
    "name": "delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
reasonNo
author_agentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description partially discloses behavior: 'Git keeps history, so it's recoverable' indicates non-permanence, but doesn't specify side effects, authorization needs, or return format details beyond the stated return object.

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 extremely concise (two short sentences) with no extraneous text. However, it may be too minimal, missing critical details, but within the conciseness dimension it scores well for brevity.

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

Completeness2/5

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

Given three parameters, no output schema, and no annotations, the description is incomplete. It fails to explain the 'reason' and 'author_agent' parameters, and doesn't specify behavior for non-existent files or confirmation requirements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% parameter description coverage, and the description adds no information about the three parameters (path, reason, author_agent). The agent must rely solely on parameter names, which is insufficient for correct invocation.

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?

The description clearly states 'Delete a memory file.' which identifies the verb and resource. It distinguishes from siblings like read, write, list by indicating a destructive action, though not explicitly contrasting them.

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 use this tool versus alternatives like write or search. The description lacks context about prerequisites or conditions, leaving the agent to infer.

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