Skip to main content
Glama
n24q02m

Mnemo - Persistent AI Memory

help

Read-onlyIdempotent

Access documentation for memory and configuration tools to understand how to manage persistent AI memory with hybrid search and cross-machine synchronization.

Instructions

Full documentation for memory and config tools. topic: 'memory' | 'config'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNomemory

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function that loads and returns documentation for specified topics (memory or config). Validates topic parameter against whitelist, loads markdown file from mnemo_mcp.docs package using importlib.resources, and returns content or error JSON.
    async def help(topic: str = "memory") -> str:
        """Load full documentation for a tool."""
        docs_package = pkg_resources.files("mnemo_mcp.docs")
        valid_topics = {"memory": "memory.md", "config": "config.md"}
    
        filename = valid_topics.get(topic)
        if not filename:
            return _json(
                {
                    "error": f"Unknown topic: {topic}",
                    "valid_topics": list(valid_topics.keys()),
                }
            )
    
        doc_file = docs_package / filename
        content = doc_file.read_text(encoding="utf-8")
        return content
  • Registration of the 'help' tool with FastMCP decorator. Defines tool metadata including description, title, and behavior hints (read-only, non-destructive, idempotent).
    @mcp.tool(
        description="Full documentation for memory and config tools. topic: 'memory' | 'config'",
        annotations=ToolAnnotations(
            title="Help",
            readOnlyHint=True,
            destructiveHint=False,
            idempotentHint=True,
            openWorldHint=False,
        ),
    )
  • Schema definition: accepts 'topic' parameter (default 'memory'), validated against valid_topics dict. Returns string (either markdown content or JSON error).
    async def help(topic: str = "memory") -> str:
Behavior4/5

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

Annotations provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, covering safety and idempotency. The description adds value by specifying it's for 'Full documentation', which clarifies the tool's behavior as informational rather than operational, aligning with annotations without contradiction. However, it doesn't detail aspects like response format or any rate limits.

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 a single, efficient sentence that front-loads the key information ('Full documentation for memory and config tools') and specifies the parameter options clearly. There is no wasted text, making it highly concise and well-structured.

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 tool's low complexity (1 parameter, no nested objects) and the presence of annotations and an output schema, the description is reasonably complete. It covers the purpose and parameter usage adequately, though it could benefit from more explicit guidance on when to use this tool versus the siblings.

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?

The description specifies the 'topic' parameter can be 'memory' or 'config', adding semantic meaning beyond the schema's generic 'Topic' title and 0% description coverage. With only one parameter and no schema descriptions, this compensates well, though it doesn't explain the default value or other nuances.

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

Purpose3/5

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

The description states the tool provides 'Full documentation for memory and config tools' which clarifies its purpose as a documentation resource. However, it doesn't specify the action verb (e.g., 'retrieve', 'display', 'show') and only mentions the two topics without distinguishing this tool from its siblings 'config' and 'memory' tools themselves.

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 by specifying the two topics ('memory' and 'config'), suggesting this tool is for getting documentation about those specific tools. However, it doesn't explicitly state when to use this tool versus directly invoking the sibling tools or provide any exclusions or alternatives, leaving usage context somewhat implied.

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/n24q02m/mnemo-mcp'

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