Skip to main content
Glama

store

Store AI memories with tags, context, importance levels, and namespaces for persistent organization and retrieval in the NeverOnce MCP server.

Instructions

Store a memory.

Args:
    content: The memory content to store.
    tags: Comma-separated tags (e.g. "preference,ui,dark-mode").
    context: When/where this memory applies.
    importance: 1-10, how important this memory is.
    namespace: Namespace for organizing memories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes
tagsNo
contextNo
importanceNo
namespaceNodefault

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'store' MCP tool definition and handler implementation in neveronce/server.py, which uses the Memory object to store data.
    @mcp.tool()
    def store(content: str, tags: str = "", context: str = "",
              importance: int = 5, namespace: str = "default") -> str:
        """Store a memory.
    
        Args:
            content: The memory content to store.
            tags: Comma-separated tags (e.g. "preference,ui,dark-mode").
            context: When/where this memory applies.
            importance: 1-10, how important this memory is.
            namespace: Namespace for organizing memories.
        """
        mem = _get_mem()
        tag_list = [t.strip() for t in tags.split(",") if t.strip()] if tags else []
        mid = mem.store(content, tags=tag_list, context=context,
                        importance=importance, namespace=namespace)
        return f"Stored memory #{mid}"
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It successfully conveys parameter constraints (1-10 importance scale, comma-separated tags) but omits behavioral details like idempotency rules, duplicate handling, or persistence guarantees.

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

Conciseness4/5

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

The description is efficiently structured with a concise purpose statement followed by an Args block. Every line adds value beyond the schema. Minor deduction for the list format which could be redundant if the schema were well-documented, but necessary given the 0% coverage.

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 5 parameters with zero schema coverage, the description adequately documents all inputs through the Args section. The existence of an output schema reduces the need to describe return values, though the description could still benefit from mentioning side effects or error conditions.

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% (only titles provided). The Args section comprehensively compensates by defining all 5 parameters with semantic meaning, format specifications (e.g., comma-separated tags with example), and valid ranges (1-10 importance) that the schema lacks.

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 core action with 'Store a memory' (specific verb + resource). While it implicitly contrasts with siblings like 'recall' and 'forget', it does not explicitly differentiate when to use this versus similar memory-related operations.

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?

The description provides no guidance on when to invoke this tool versus alternatives such as 'correct' or 'check', nor does it mention prerequisites, initialization requirements, or post-conditions.

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/WeberG619/neveronce'

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