Skip to main content
Glama

Delete from my memory locker

locker_delete
DestructiveIdempotent

Delete one exact key (no folders or wildcards) and its value from your memory locker, for good (no undo), freeing its space. Answers deleted: true, or 404 item_not_found for an unknown key (nothing changes). To change a value, call locker_put again instead (it replaces it); locker_list finds keys. Works after the plan ended too.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "notes/plan.md",
      "instance_id": "lkr_exampleexampleexample2"
    },
    "name": "locker_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesKey, 1 to 200 characters from A-Z a-z 0-9 . _ : / - (no spaces; "/" separates folders; no empty, "." or ".." part).
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / key / description
      Previous value: -"Key, 1 to 200 characters from A-Z a-z 0-9 . _ : / - (no spaces; \"/\" separates folders)."New value: +"Key, 1 to 200 characters from A-Z a-z 0-9 . _ : / - (no spaces; \"/\" separates folders; no empty, \".\" or \"..\" part)."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "lkr_exampleexampleexample2",
      +    "key": "notes/plan.md"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  3. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  4. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / key / description
      Added value: +"Key, 1 to 200 characters from A-Z a-z 0-9 . _ : / - (no spaces; \"/\" separates folders)."
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
  5. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds substance beyond that: deletion is permanent with no undo, it frees space, an unknown key returns 404 item_not_found with nothing changed, and it works even after the plan ended. That is real operational context, not restatement.

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?

The destructive action and scope lead the first sentence, followed by outcome, alternatives, and a durability note. Every parenthetical carries information; there is no filler.

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

Completeness5/5

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

Despite no output schema, the description documents both the success response (deleted: true) and the failure mode (404 item_not_found, nothing changes). For a 3-parameter destructive tool this covers everything an agent needs to call it safely.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds matching semantics not spelled out in the schema: the key must be exact, with no folder expansion or wildcard behavior. Minor added value over an already well-documented schema.

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 and resource ('delete one exact key ... from your memory locker') and immediately bounds the scope ('no folders or wildcards'), so an agent can distinguish it from locker_put and locker_list without opening the schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: to change a value use locker_put (it replaces), and locker_list finds keys. It also states the negative case (folders/wildcards not supported), giving both when-to-use and when-not-to-use guidance.

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.