Skip to main content
Glama
egoughnour

Massive Context MCP

by egoughnour

rlm_store_result

Store a sub-call result with an identifier and optional metadata to aggregate results from large dataset processing, enabling recursive chunking and analysis beyond standard context limits.

Instructions

Store a sub-call result for later aggregation.

Args: name: Result set identifier result: Result content to store metadata: Optional metadata about this result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
resultYes
metadataNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler function for the rlm_store_result tool. It stores a sub-call result to a JSONL file under RESULTS_DIR for later aggregation. Decorated with @mcp.tool() to register it as a FastMCP tool.
    @mcp.tool()
    async def rlm_store_result(
        name: str,
        result: str,
        metadata: Optional[dict] = None,
    ) -> str:
        """Store a sub-call result for later aggregation.
    
        Args:
            name: Result set identifier
            result: Result content to store
            metadata: Optional metadata about this result
        """
        results_file = RESULTS_DIR / f"{name}.jsonl"
        with open(results_file, "a") as f:
            f.write(json.dumps({"result": result, "metadata": metadata or {}}) + "\n")
    
        return f"Result stored to '{name}'"
  • The tool is registered with FastMCP via the @mcp.tool() decorator on the rlm_store_result function. This is the registration mechanism.
    @mcp.tool()
    async def rlm_store_result(
        name: str,
        result: str,
        metadata: Optional[dict] = None,
    ) -> str:
  • Type annotations serve as the schema: name (str), result (str), metadata (Optional[dict]), and return type str.
    async def rlm_store_result(
        name: str,
        result: str,
        metadata: Optional[dict] = None,
    ) -> str:
        """Store a sub-call result for later aggregation.
    
        Args:
            name: Result set identifier
            result: Result content to store
            metadata: Optional metadata about this result
  • RESULTS_DIR is defined as DATA_DIR / 'results', the directory where store_result writes JSONL files.
    RESULTS_DIR = DATA_DIR / "results"
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions storing but omits details like overwrite behavior, size limits, idempotency, or any required context. This is insufficient for safe invocation.

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 concise with a clear docstring format, immediately stating the purpose and listing parameters with brief explanations. No extraneous content.

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

Completeness3/5

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

Given the presence of an output schema (not shown), return value explanation is not required. However, the description lacks behavioral context (e.g., side effects, dependencies) and usage guidelines, making it only partially complete for a tool with 3 parameters.

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 coverage, the description adds meaningful context: 'name: Result set identifier', 'result: Result content to store', 'metadata: Optional metadata about this result'. This clarifies each parameter's role, though additional constraints (e.g., format, length) are missing.

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 'Store a sub-call result for later aggregation', which identifies the verb and resource. However, it does not differentiate from sibling tools like rlm_get_results or rlm_sub_query, though the purpose is generally clear.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites or context where storing is appropriate, leaving the agent without clear decision criteria.

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/egoughnour/massive-context-mcp'

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