Skip to main content
Glama

memory_create_section

Organize memories by creating section headers for grouping related content without embedding or visualization.

Instructions

Create a new section/subsection header memory.

Section memories are organizational placeholders that:

  • Are NOT visible in the graph visualization

  • Are NOT included in duplicate detection

  • Do NOT compute embeddings or cross-references

Args: content: Title/description of the section section: Parent section name (e.g., "Architecture", "API") subsection: Subsection path (e.g., "endpoints/auth")

Returns: Created section memory with auto-assigned tag "memora/sections"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes
sectionNo
subsectionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the `memory_create_section` tool. It creates a memory of type 'section' and assigns it the 'memora/sections' tag. It uses the `_create_memory` helper to persist the memory to the database.
    async def memory_create_section(
        content: str,
        section: Optional[str] = None,
        subsection: Optional[str] = None,
    ) -> Dict[str, Any]:
        """Create a new section/subsection header memory.
    
        Section memories are organizational placeholders that:
        - Are NOT visible in the graph visualization
        - Are NOT included in duplicate detection
        - Do NOT compute embeddings or cross-references
    
        Args:
            content: Title/description of the section
            section: Parent section name (e.g., "Architecture", "API")
            subsection: Subsection path (e.g., "endpoints/auth")
    
        Returns:
            Created section memory with auto-assigned tag "memora/sections"
        """
        # Build metadata
        metadata: Dict[str, Any] = {
            "type": "section",
        }
        if section:
            metadata["section"] = section
        if subsection:
            metadata["subsection"] = subsection
    
        # Create with auto-tag
        tags = ["memora/sections"]
    
        try:
            record = _create_memory(content.strip(), metadata, tags)
        except ValueError as exc:
            return {"error": "invalid_input", "message": str(exc)}
    
        _schedule_cloud_graph_sync()
        return {"memory": record}
Behavior5/5

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

With no annotations provided, the description carries full disclosure burden and excels by listing three critical behavioral exclusions (no graph visibility, no duplicate detection, no embeddings/cross-references) and noting the auto-assigned tag 'memora/sections' that agents can expect in the output.

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 uses a clean, scannable structure with a purpose statement, bullet points for behavioral traits, and labeled Args/Returns sections. Every sentence provides value; no repetition of schema structure or redundant phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of an output schema, the description appropriately summarizes the return value (noting the auto-assigned tag) without over-explaining. It comprehensively covers the tool's unique behavior, parameters, and hierarchical positioning relative to the memory system.

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?

Despite 0% schema description coverage, the Args section fully compensates by documenting all three parameters with semantic meaning ('Title/description', 'Parent section name') and concrete examples for section ('Architecture', 'API') and subsection ('endpoints/auth').

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 opens with a specific verb ('Create') and resource ('section/subsection header memory'), and immediately distinguishes this tool from siblings like memory_create by defining these as organizational placeholders with specific exclusionary traits (NOT visible in graph, NOT in duplicate detection).

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 provides clear context for when to use this tool (creating organizational structure) through the negative constraints that differentiate it from regular memories. However, it stops short of explicitly naming sibling alternatives like memory_create or stating 'use this instead of X when organizing hierarchically.'

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