Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Agent memory, list keys: what a namespace holds

memory_list
Read-only

List up to 100 keys saved in your namespace, optionally only those starting with a prefix, with their size, save time and expiry; pass the returned cursor for the next page. Values are not included (read them with /memory/get). Values are kept until they expire (at most 30 days) or are deleted; reads anywhere may lag a write made elsewhere by up to a minute. Use to see what an agent has saved. Example: namespace=demo-agent-memory-7f3c9a21. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "namespace": "<namespace>"
    },
    "name": "memory_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoThe cursor from the previous page of this list
prefixNoOnly keys that start with this text
namespaceYesYour namespace: a secret of 16 to 128 letters, digits, - or _ that you choose and reuse. Anyone who knows it can read and write it, so treat it like a password; send it in a POST body to keep it out of URLs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: eventual consistency ('reads anywhere may lag a write made elsewhere by up to a minute'), retention ('kept until they expire (at most 30 days) or are deleted'), and full cost mechanics ('$0.002/call via x402 USDC or a card key... first 25 free; failed calls free'). The per-call billing note also explains the otherwise puzzling idempotentHint=false on a read tool, so nothing contradicts the annotations.

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 operation and its output fields, then behavior, then pricing — a sensible ordering with no wasted preamble. A few clauses are redundant ('Use to see what an agent has saved' restates the opening) and the payment details are dense, but each block carries distinct information.

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?

There is no output schema, and the description compensates by enumerating the returned fields (size, save time, expiry, cursor) and explaining the paging contract. Retention, staleness, and cost — the three things an agent could get wrong here — are all covered.

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 meaning beyond the schema: the 100-key page cap (absent from the schema), the paging loop ('pass the returned cursor for the next page'), and a concrete namespace example. Prefix semantics are only echoed, not extended.

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?

Opens with a specific verb and resource ('List up to 100 keys saved in your namespace') and immediately bounds the scope with the prefix option and the page-size cap. It also states what is NOT returned ('Values are not included (read them with /memory/get)'), which cleanly separates it from the sibling read tool.

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 an explicit use case ('Use to see what an agent has saved') and routes the agent to /memory/get when values are actually needed, which is the key alternative here. It does not state a when-not condition or a preferred ordering relative to memory_set/memory_delete, so it stops short of 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.