Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Forget a memory

forget
DestructiveIdempotent

Delete a saved Memory item by its id to prevent it from reappearing across devices. Re-creatable, so no confirmation required.

Instructions

Delete a saved Memory item by its id (from list_memory). Records a cross-device delete so it doesn’t come back. Minor + re-creatable (you can remember it again), so no confirm needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesthe memory item id (from list_memory)
brandNoprofile id/name from list_brands, this call only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / brand / description
      Previous value: -"brand id/name from list_brands, this call only"New value: +"profile id/name from list_brands, this call only"
  2. Changed1 schema field changedv0.1.371
    • addedInput schema / properties / brand
      Added value: +{
+  "description": "brand id/name from list_brands, this call only",
+  "type": "string"
+}
  3. Addedv0.1.161

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's added value is the cross-device delete behavior (it won't come back) and the re-creatable/reversible nature that justifies skipping confirmation. That is genuine context beyond the annotation flags, though it doesn't cover error cases (e.g., unknown id) or response behavior.

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?

Three tight sentences with the action and key front-loaded, then persistence behavior, then the confirmation rationale. No filler.

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 single-parameter destructive tool with no output schema, the description covers action, key source, durability, and reversibility. Minor gap: no mention of failure behavior for an invalid or already-deleted 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 id parameter is already documented as coming from list_memory, so the description mostly restates the schema. The optional brand parameter ('this call only') is never addressed in the description.

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?

States a specific verb (Delete) and resource (a saved Memory item) plus the lookup key (id from list_memory), which cleanly separates it from siblings like list_memory, remember, and tidy_memory.

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

Usage Guidelines4/5

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

Gives clear context: the id comes from list_memory, and it explicitly says no confirmation is needed because the action is minor and re-creatable. It does not name when to prefer tidy_memory or other memory-management siblings, but the routing for this tool is unambiguous.

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