openmem-mcp

Overview Schema Source Related Servers Discussions Admin

Read a compressed tool result

smart_compact_get

Read-onlyIdempotent

Retrieve the full text of a compressed tool result using its 16-character hex ID. Supports offset paging when output exceeds 100,000 characters.

Instructions

Return the full text of a tool result the context proxy compressed, by the 16-hex id from [openmem: tool result compressed … smart_compact_get(id="")] or a smart_compact_search blob_ids entry. Output is capped at 100000 characters; pass offset (next_offset) to page.

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": {
      "id": "<id>"
    },
    "name": "smart_compact_get"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Blob id: exactly 16 lowercase hex characters
`offset`	No	Character offset to start from (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.8.0Oct 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior. The description adds genuinely useful context beyond that: output is capped at 100000 characters and can be paged via offset/next_offset, which prevents an agent from assuming it always receives the entire blob.

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?

Two compact sentences, front-loaded with purpose and immediately followed by id provenance and paging behavior. No repetition or wasted 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?

For a simple read retrieval tool, the description covers purpose, id source, output cap, and paging. No output schema exists, but the description supplies the essential return-shape constraint (100000 characters) and continuation mechanism.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds provenance for the id (context-proxy marker or search blob_ids) and clarifies the paging role of offset (next_offset). It does not add syntax details beyond the schema, but the added meaning is real.

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?

States a specific verb and resource: 'Return the full text of a tool result the context proxy compressed,' and identifies the key input. This clearly distinguishes it from smart_compact_search, which produces blob ids rather than returning text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains exactly how to obtain the id — from the [openmem: tool result compressed …] marker or a smart_compact_search blob_ids entry — and when to use offset for paging. An agent has all routing information needed.

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