Skip to main content
Glama

ui_delete_memory

Deletes a project memory entry through the app's UI using the specified project ID and memory ID.

Instructions

App-only: delete a project memory entry from the UI.

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

Input Schema

NameRequiredDescriptionDefault
memory_idYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Delete' signals a destructive mutation, but nothing is said about permanence, reversibility, required permissions, or what happens if the memory or project does not exist.

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?

A single short sentence with the scope qualifier front-loaded and no wasted wording. It is efficient, though its brevity is part of why other dimensions are thin.

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?

For an unannotated destructive mutation with no output schema and zero parameter documentation, the description is too sparse. An agent gets no information on irreversibility, error conditions, or return behavior before committing to a delete.

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

Parameters2/5

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

Schema description coverage is 0% for both required parameters, so the description must compensate and it does not. It only alludes to a 'project memory entry', leaving the meaning of project_id vs memory_id and their formats undocumentsed.

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 gives a specific verb (delete) and resource (a project memory entry) plus a scoping qualifier ('App-only ... from the UI'). This distinguishes it from the plain 'memory_delete' sibling by implication, though it never names that alternative.

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

Usage Guidelines3/5

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

'App-only' implies this is the UI-path counterpart to a non-UI delete, which hints at when to prefer it. However, there is no explicit when-to-use vs when-not-to-use statement and no named alternative, leaving routing to inference from sibling names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.