Skip to main content
Glama

List my memory locker

locker_list
Read-only

List keys in your memory locker, sorted, with sizes and types but no values (locker_get reads one), plus the locker's usage. prefix keeps only keys that start with it. While next_after is not null, call again with after = next_after for the next page.

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": {
      "limit": 50,
      "prefix": "notes/",
      "instance_id": "lkr_exampleexampleexample2"
    },
    "name": "locker_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNonext_after of your previous call: only keys after it.
limitNoKeys per call, 1 to 1000 (default 200).
prefixNoOnly keys starting with this, e.g. "notes/".
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. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "lkr_exampleexampleexample2",
      +    "limit": 50,
      +    "prefix": "notes/"
      +  }
      +]
    • 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."
  2. 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}$"
  3. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / after
      Added value: +{
      +  "description": "next_after of your previous call: only keys after it.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Keys per call, 1 to 1000 (default 200).",
      +  "maximum": 1000,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • 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 / prefix / description
      Added value: +"Only keys starting with this, e.g. \"notes/\"."
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: results are sorted, values are omitted, the response includes locker usage, and pagination is driven by a next_after field. What it does not describe is the shape of the 'usage' block, which is the only remaining gap.

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 dense sentences, each doing distinct work: what is returned, how to filter, how to paginate. The exclusions ('no values') and the sibling handoff are front-loaded. 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 5-parameter read-only list tool with no output schema, the description covers the essentials: result contents, sort order, filtering, and the pagination loop. The return payload is only sketched (key, size, type, usage), so an agent still learns the exact field names at call time, but nothing needed to invoke it correctly is missing.

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 the cross-field contract the schema cannot express: the output's next_after becomes the input's after. It also restates the prefix semantics usefully. It says nothing about limit, instance_id, or passport_token, which the schema handles.

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 ('List keys in your memory locker') and immediately scopes the output ('sorted, with sizes and types but no values'), then names the sibling that retrieves values ('locker_get reads one'). An agent can distinguish this from locker_get 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 value retrieval to locker_get, explains that 'prefix keeps only keys that start with it', and gives the exact pagination rule: 'While next_after is not null, call again with after = next_after'. Both the when-to-use and the loop-termination condition are 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.