Skip to main content
Glama

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

Agent memory, save: key value store for agents

memory_set
DestructiveIdempotent

Save a value (up to 8,000 characters of text or JSON) under a key in your own namespace, so an agent can remember facts, preferences or task state between runs. Overwrites an existing key; expires after 1 to 30 days (default 30). 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 persist what an agent learned for a later call to memory_get. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Changes only what you saved in your own memory namespace; 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>",
      "value": "<value>"
    },
    "name": "memory_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe key, up to 200 characters
daysNoDays to keep it, 1 to 30 (default 30)
valueYesThe text or JSON to save, up to 8,000 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

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations: overwrite semantics, TTL range and default, retention until expiry or deletion, up-to-one-minute cross-region read lag, and the full billing model (per-call charge, 25 free, failed calls free). The overwrite/TTL disclosure meaningfully elaborates destructiveHint=true, and the pricing detail is behavioral context no annotation carries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Expiry is stated twice in near-identical terms ("expires after 1 to 30 days" then "kept until they expire (at most 30 days)"), and the pricing sentence stacks clauses ("$0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free"). The core purpose is front-loaded, but the middle of the description is redundant and could be trimmed by a third.

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 write tool with no output schema it covers scope, overwrite, retention, eventual consistency and cost — essentially everything an agent needs to decide and call safely. The only gap is that it never indicates what a successful save returns or how failure is signaled, which the absent output schema leaves to the description.

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%, so key, value, days and namespace are already fully documented in the schema. The description repeats the 8,000-character value cap and the 1-30 day window without adding syntax or format guidance beyond it, so baseline 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 and resource ("Save a value ... under a key in your own namespace") plus the value limits, and explicitly frames the purpose as cross-run agent memory. It distinguishes itself from the retrieval sibling by naming memory_get as the follow-up call.

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?

"Use to persist what an agent learned for a later call to memory_get" gives clear usage context and names the natural alternative. It doesn't explicitly exclude memory_list/memory_delete or warn against using this as a general-purpose store, but the intended niche is unambiguous.

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.