Skip to main content
Glama

Store in my memory locker

locker_put
DestructiveIdempotent

Store a value in your memory locker under a key (survives between sessions). Send exactly one of value (text) or value_base64 (bytes). The answer holds the value's etag: pass it as if_match next time so that a run that overlaps yours cannot be overwritten without notice.

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",
      "value": "Step 1 done.",
      "instance_id": "lkr_exampleexampleexample2"
    },
    "name": "locker_put"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesKey, 1 to 200 characters from A-Z a-z 0-9 . _ : / - (no spaces; "/" separates folders; no empty, "." or ".." part).
valueNoThe value as text (UTF-8), up to 1 MB. "" stores an empty value.
if_matchNoStore only if the current value has this etag (from locker_get or locker_put); "*": only if the key exists. Otherwise 412 precondition_failed and nothing is stored.
instance_idYesUtility instance id from buy or list_utilities.
content_typeNoStored and returned on read. Default text/plain; charset=utf-8 for value, application/octet-stream for value_base64.
value_base64NoThe value as bytes (up to 1 MB), in standard base64 with = padding.
if_none_matchNo"*": store only if the key does not exist yet (create only), else 412 precondition_failed.
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. Changed3 schema fields 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)."
    • changedInput schema / properties / value / description
      Previous value: -"The value as text (UTF-8). \"\" stores an empty value."New value: +"The value as text (UTF-8), up to 1 MB. \"\" stores an empty value."
    • changedInput schema / properties / value_base64 / description
      Previous value: -"The value as bytes, in standard base64 with = padding."New value: +"The value as bytes (up to 1 MB), in standard base64 with = padding."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "lkr_exampleexampleexample2",
      +    "key": "notes/plan.md",
      +    "value": "Step 1 done."
      +  }
      +]
    • 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. Changed8 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / content_type / description
      Added value: +"Stored and returned on read. Default text/plain; charset=utf-8 for value, application/octet-stream for value_base64."
    • addedInput schema / properties / if_match
      Added value: +{
      +  "description": "Store only if the current value has this etag (from locker_get or locker_put); \"*\": only if the key exists. Otherwise 412 precondition_failed and nothing is stored.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "pattern": "^[\\x20-\\x7e]+$",
      +  "type": "string"
      +}
    • addedInput schema / properties / if_none_match
      Added value: +{
      +  "const": "*",
      +  "description": "\"*\": store only if the key does not exist yet (create only), else 412 precondition_failed.",
      +  "type": "string"
      +}
    • 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."
    • addedInput schema / properties / value / description
      Added value: +"The value as text (UTF-8). \"\" stores an empty value."
    • addedInput schema / properties / value_base64 / description
      Added value: +"The value as bytes, in standard base64 with = padding."
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true; the description earns credit by explaining the concurrency contract (etag as if_match, so overlapping runs cannot silently overwrite) and by flagging the mutually exclusive text/bytes inputs. It never spells out that an unconditional put overwrites existing data destructively, nor mentions the 1 MB ceiling or auth surface, leaving some of the mutation risk implicit.

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?

Two sentences, both front-loaded with the operation then the safety contract; no filler, no repetition of schema detail, and the most load-bearing constraint (one-of value/value_base64) arrives before the etag advice.

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 an 8-parameter write tool with no output schema, the description covers the core operation, input exclusivity, and the return-value hook ("the answer holds the value's etag"). Remaining gaps — overwrite-on-unconditional-put wording and error paths beyond 412 — are partly mitigated by a fully described 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 per-parameter meaning is already carried by the schema; the correct baseline is 3. The one genuinely additive fact is the exclusive-or between value and value_base64, which the schema does not encode — worth noting but not enough to lift the dimension much, and the etag/if_match relationship is already documented in the schema for that property.

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 ("Store a value in your memory locker under a key") plus its persistence scope ("survives between sessions"), which cleanly separates it from the locker_get/locker_list/locker_delete siblings by verb alone.

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 concrete usage rules: send exactly one of value or value_base64, and carry the returned etag forward as if_match on the next write. It stops short of explicitly naming when to prefer locker_get or locker_delete, or when a write should be skipped, so it is clear context rather than full routing 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.