Skip to main content
Glama

agoragentic_memory_read

Read-onlyIdempotent

Retrieve stored data from persistent agent memory by reading specific keys or listing all available keys within a namespace.

Instructions

Read from your persistent agent memory. Free, no cost to recall your own data. Returns a single key or lists all keys.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoSpecific key to read. Omit to list all stored keys.
namespaceNoNamespace to read fromdefault
prefixNoFilter keys by prefix when listing all keys

Implementation Reference

  • The handler implementation for the agoragentic_memory_read tool, which performs a GET request to the Agoragentic API to retrieve memory values.
    def agoragentic_memory_read(key: str = "", namespace: str = "default") -> str:
        """Read from persistent agent memory. FREE."""
        try:
            params = {"namespace": namespace}
            if key:
                params["key"] = key
            resp = requests.get(f"{AGORAGENTIC_BASE_URL}/api/vault/memory", params=params, headers=_headers(), timeout=15)
            return json.dumps(resp.json(), indent=2)
        except Exception as e:
            return json.dumps({"error": str(e)})
  • The schema definition for the agoragentic_memory_read tool within the AutoGen integration.
    {"name": "agoragentic_memory_read", "description": "Read from persistent memory. FREE.",
     "parameters": {"type": "object", "properties": {
         "key": {"type": "string"}, "namespace": {"type": "string", "default": "default"}
     }}},
  • Registration of the agoragentic_memory_read function in the FUNCTION_MAP for AutoGen usage.
    "agoragentic_memory_read": agoragentic_memory_read,
Behavior4/5

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

Annotations already cover read-only, non-destructive, idempotent, and open-world characteristics. The description adds valuable context about cost ('Free, no cost') and clarifies the dual behavior (returns single key OR lists all keys), which isn't captured in annotations. No contradiction with annotations.

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?

Two concise sentences that efficiently convey purpose, cost, and behavior. Every word earns its place with no redundancy or fluff. Well-structured with front-loaded main functionality.

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 rich annotations covering safety and behavior, and 100% schema coverage for parameters, the description provides good contextual completeness. It adds useful behavioral context about cost and dual return modes. The main gap is lack of output format details (no output schema), but the description partially compensates by mentioning return types.

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 description coverage is 100%, so parameters are fully documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., doesn't explain key format, namespace purpose, or prefix usage). Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Read from your persistent agent memory') and resource ('agent memory'), distinguishing it from write operations. However, it doesn't explicitly differentiate from sibling tools like 'agoragentic_search' or 'agoragentic_secret_retrieve' that might also involve data retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context through 'Free, no cost to recall your own data' and mentions two modes (single key vs. list all), but doesn't explicitly state when to use this tool versus alternatives like 'agoragentic_search' or 'agoragentic_secret_retrieve'. The input schema provides some guidance with the optional 'key' parameter.

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/rhein1/agoragentic'

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