Skip to main content
Glama

forget_me

DestructiveIdempotent

Delete your resort profile, guest notes, bundles and snapshots and revoke all sessions. Requires agent_id and session. Payment reconciliation hashes remain for 30 days.

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": {
      "agent_id": "<agent_id>",
      "session": "<session>"
    },
    "name": "forget_me"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYesPrivate bearer capability returned by check_in. Never put it in a URL.
agent_idYesServer-signed private returning-guest credential. Redact from logs and transcripts; never put in URLs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 job is to add context and it does: it discloses that sessions are revoked as a side effect and that payment reconciliation hashes are retained for 30 days. It does not spell out that the deletion is irreversible or whether confirmation is required, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the destructive scope before the prerequisites and retention caveat. The middle sentence, 'Requires agent_id and session', is largely redundant with the schema's required array and is the only sentence that does not fully earn its place.

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, irreversible-looking operation with annotations covering safety and no output schema, the description supplies the missing pieces an agent needs: full deletion scope, session revocation side effect, and 30-day retention exception. What is missing is minimal — notably no statement on whether the action can be undone.

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% and both parameters carry rich descriptions plus patterns, so the schema does the heavy lifting. The description only restates that both are required, adding no format, sensitivity, or handling guidance beyond what is already structured.

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 leads with a specific verb, 'Delete', followed by an enumerated resource list (resort profile, guest notes, bundles, snapshots) plus an explicit secondary effect ('revoke all sessions'). That scope enumeration is what separates it from the narrower revoke_sessions sibling and from the mutating restore tool, so an agent can select it without opening a schema.

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?

It states the prerequisites ('Requires agent_id and session') and implies a full-account teardown, but never says when to choose this over siblings such as revoke_sessions (sessions only) or restore, nor does it name any explicitly excluded case. Usage is inferable from the scope list rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources