Skip to main content
Glama

memory_get

Retrieve specific stored memories by ID from the Memora server, with options to include or exclude image data for optimized response handling.

Instructions

Retrieve a single memory by id.

Args: memory_id: ID of the memory to retrieve include_images: If False, strip image data from metadata to reduce response size

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memory_idYes
include_imagesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the `memory_get` MCP tool, which retrieves a memory by ID from the database using `_get_memory` and optionally filters out image metadata.
    async def memory_get(memory_id: int, include_images: bool = False) -> Dict[str, Any]:
        """Retrieve a single memory by id.
    
        Args:
            memory_id: ID of the memory to retrieve
            include_images: If False, strip image data from metadata to reduce response size
        """
        record = _get_memory(memory_id)
        if not record:
            return {"error": "not_found", "id": memory_id}
    
        metadata = record.get("metadata") or {}
        if not include_images and metadata.get("images"):
            record["metadata"]["images"] = [
                {"caption": img.get("caption", "")} for img in metadata["images"]
            ]
    
        return {"memory": record}
Behavior3/5

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

Since no annotations are provided, the description carries the full burden. It adds valuable behavioral context about the include_images parameter stripping image data 'to reduce response size,' which explains performance implications. However, it fails to indicate whether this is a safe read-only operation or if there are side effects.

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?

Extremely concise with no wasted words. Front-loaded one-line purpose statement followed by structured Args documentation. Every sentence 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?

Adequate for a simple two-parameter retrieval tool. Since an output schema exists, the description appropriately omits return value details. Documents all parameters given the schema's lack of descriptions. Minor gap: lacks safety/disposition indication (read-only vs destructive) which would be helpful given no annotations.

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?

With 0% schema description coverage, the description compensates effectively by documenting both parameters in the Args section. It explains memory_id purpose and details the optimization behavior of include_images ('strip image data from metadata'), adding meaning beyond just the parameter name.

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?

States specific verb ('Retrieve'), resource ('memory'), and scope ('single memory by id'). The 'by id' qualifier implicitly distinguishes it from sibling tools like memory_list or memory_semantic_search, though it could explicitly name alternatives for clarity.

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

Usage Guidelines2/5

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

Provides no guidance on when to use this tool versus siblings like memory_list, memory_semantic_search, or memory_hybrid_search. No mention of prerequisites (e.g., needing to obtain the ID from another tool) or when not to use it.

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/agentic-box/memora'

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