Skip to main content
Glama

agent_memory

Store and retrieve persistent data across agent sessions using Cloudflare KV. Read, write, or delete memory keys to maintain state between interactions.

Instructions

Read or write persistent agent memory across sessions.

Agents are stateless — use this to store and retrieve data between
sessions. Data is stored in Cloudflare KV and persists indefinitely.

Parameters:
    key    — Unique memory key to read or write (e.g. "user_preferences").
    value  — For action="set": JSON string of the value to store.
             For action="get" or action="delete": ignored.
    action — One of: "get" (read existing value), "set" (write value),
             "delete" (remove the key). Default: "get".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
valueNo
actionNoget

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses that data is stored in Cloudflare KV and persists indefinitely, and details the behavior of each action (get, set, delete). No annotations are provided, so the description carries the full burden; it does so adequately.

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?

The description is concise, front-loads the main purpose, and uses bullet points for parameter details. Every sentence adds value with no redundancy.

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?

Given the presence of an output schema and the tool's simplicity, the description covers input semantics thoroughly. It could mention error handling or limits, but is complete for typical use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description adds significant value by explaining each parameter's purpose, including conditional usage for 'value' and enumeration of 'action' with defaults.

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?

The description clearly states the verb (read/write) and resource (persistent agent memory across sessions), distinguishing it from stateless agent behavior. The tool's purpose is unambiguous.

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?

The description explicitly advises using this tool when agents need persistent memory across sessions, contrasting with statelessness. It does not mention exclusions or alternative tools, but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scotia1973-bot/api-hub'

If you have feedback or need assistance with the MCP directory API, please join our Discord server