Skip to main content
Glama
Sign In
Loom

Loom

by MlkBlk-IT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Ctx Store

ctx_store
Idempotent

Store bulky content locally to shrink prompts, returning a dense anchor and stable IDs so the original bytes can be retrieved later.

Instructions

Move bulky content out of the prompt into a local drawer, without losing any of it.

Returns a dense anchor (the parts that must stay in context) plus stable IDs so the original bytes can be retrieved later with ctx_get.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content": "<content>"
    },
    "name": "ctx_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoshort human-readable name, e.g. "build.log"
contentYesthe bulky text to store (log dump, file body, tool output, etc.)
session_idNological session the content belongs to ("default" or omitted = the shared "default" session)default

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations' safety and idempotency signals, the description discloses lossless preservation, local storage, a dense anchor that remains in context, and stable IDs for recovering the original bytes. It does not discuss retention, storage limits, or what idempotent repeated stores mean, but it provides meaningful operational context.

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 compact and front-loads the core action and benefit. Its second sentence efficiently explains the returned context artifact and the retrieval workflow without redundant wording.

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?

For a simple three-parameter tool with full schema coverage and an output schema, this provides enough context to select and invoke it correctly. The main remaining gap is selection guidance among the three storage siblings, along with minor unspecified storage-lifecycle details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already explains content, label, and session_id. The description reinforces the purpose of storing bulky content but adds no parameter-specific formats, constraints, or session semantics beyond that structured documentation.

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 action and resource: moving bulky content out of the prompt into local storage while preserving it. It also connects storage to later retrieval with ctx_get, but does not explicitly distinguish this raw-content operation from the closer siblings ctx_store_file and ctx_store_cmd.

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 phrase 'bulky content' establishes a clear use case, and the second sentence directs the agent to ctx_get for later retrieval. It lacks explicit guidance on when to choose ctx_store_file or ctx_store_cmd instead, but the intended context is otherwise clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools