Skip to main content
Glama

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

Agent memory, recall: read a saved value

memory_get
Read-only

Read the value saved under a key in your namespace with /memory/set, with when it was saved and when it expires. A key that was never saved or has expired is a 422 and is not charged. 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 recall what an agent saved in an earlier run. Example: namespace=demo-agent-memory-7f3c9a21, key=user-preferences. 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>",
      "key": "<key>"
    },
    "name": "memory_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe key, up to 200 characters
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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, and the description genuinely adds context beyond them: 422 for missing/expired keys without charge, max 30-day retention, and up to a minute of read lag. The pricing detail also explains why idempotentHint is false (each call is billed), which reconciles the description with the annotations rather than contradicting them.

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 return shape, then error behavior, retention, and cost. The charging point is made twice ("$0.002/call... failed calls free" and "each call is charged, so repeats are not free"), which is redundant but the sentence density otherwise earns its place.

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?

Covers purpose, error semantics, retention window, staleness bound, and cost for a two-parameter read tool. With no output schema, the description does explain what is returned, so an agent has everything needed to call it and interpret failures.

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 coverage is 100%, and the schema already explains both namespace (secret, 16-128 chars, treat like a password) and key (up to 200 chars). The description only adds a worked example of the two values, so the baseline of 3 is appropriate with a small nudge from the example.

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 the value saved under a key in your namespace") and names the writing sibling (/memory/set), so an agent can tell it apart from memory_set/memory_delete/memory_list without opening schemas. It also states what comes back (value, save time, expiry), which sharpens the distinction from a bare key lookup.

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 recall what an agent saved in an earlier run") plus a concrete example with namespace and key. It does not explicitly exclude alternatives such as listing keys with memory_list, so it lands just short of full when/when-not routing.

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.