Skip to main content
Glama

Read from my memory locker

locker_get
Read-only

Read one key's value from your memory locker (a JSON content_type as data, other text as text, bytes as base64) with its etag: pass it as if_match to locker_put to replace exactly this value. Unknown key: 404 item_not_found; locker_list finds keys.

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_get"
  }
}

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.4/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive/non-open-world, and the description adds real value beyond them: how values are decoded (JSON as data, other text as text, bytes as base64), that an etag accompanies the value, and the exact 404 item_not_found error for a missing key. It does not discuss auth/permission scope beyond the passport_token field being described in the schema.

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?

Front-loaded with the verb and resource, and every clause carries information (encoding, etag handoff, error code, discovery tool). The parenthetical and semicolon-chained error/lookup clauses make it slightly telegraphic, but nothing is wasted.

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?

With no output schema, the description correctly compensates by describing the return shape (value plus etag, with content-type-dependent decoding) and the primary failure mode (404 item_not_found). For a 3-parameter read tool this is sufficient to call it correctly and chain it into subsequent operations.

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 key format, instance_id origin, and the passport_token fallback are already fully documented in the schema. The description adds no further per-parameter meaning (it does not, for example, explain key-to-folder nesting behavior or instance scoping), so the baseline of 3 applies.

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+resource ("Read one key's value from your memory locker") and immediately narrows scope with "one key" and the value-encoding rules. An agent can distinguish it from locker_list (finding keys) and locker_put (replacing values) without opening either 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: on an unknown key use locker_list to find keys, and pass the returned etag as if_match to locker_put to replace exactly this value. This names the alternatives and the conditions that select them.

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.