Skip to main content
Glama
zihin-ai

Zihin MCP Server

by zihin-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

delete_agent_memory

Destructive

Soft-delete a specific agent memory by agent ID, memory key, and user key; use it to remove stored context while protecting platform control keys prefixed with _.

Instructions

Remove (soft delete) uma memória específica de um agente. Requer agent_id, memory_key e user_key. Chaves com prefixo "_" são controle da plataforma e não podem ser removidas por aqui.

Input Schema

NameRequiredDescriptionDefault
scopeNoEscopo da memória (default agent_user). A mesma chave pode existir em escopos diferentes.
agent_idYesUUID do agente
user_keyYesIdentificador do usuário final dono da memória
memory_keyYesChave da memória a ser removida

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.2
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "Escopo da memória (default agent_user). A mesma chave pode existir em escopos diferentes.",
+  "enum": [
+    "agent_user",
+    "tenant_user",
+    "tenant_global"
+  ],
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds genuinely new behavioral context: it is a SOFT delete (memory recoverable, not permanently purged) and platform-controlled keys are protected. These details go beyond the structured annotations.

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?

Compact and front-loaded, leading with the action and soft-delete nature, then the required inputs, then the constraint. Every sentence carries information, though the required-parameter sentence is slightly redundant with the schema.

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 destructive delete with annotations already covering the safety profile and no output schema, the description supplies the key extras (soft delete, protected keys). It omits any mention of the scope parameter's effect, but that is documented in the schema.

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 description coverage is 100%, so the schema already documents all four parameters including the scope enum. The description only restates the three required parameter names, adding no syntax or semantic value beyond the schema; 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 ('Remove (soft delete) uma memória específica de um agente'), which is precise and unambiguous. It does not explicitly differentiate itself from the sibling list_agent_memory, so it falls short of a 5.

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?

Provides one useful constraint ('Chaves com prefixo "_" são controle da plataforma e não podem ser removidas por aqui'), which tells the agent when the call will fail. However, there is no guidance on when to use this versus alternatives like list_agent_memory, nor prerequisites about scope selection.

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