Skip to main content
Glama
Sign In
engram

engram

by TushaeBXN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

engram_decompress

Decode Engram Shorthand (ES) into readable natural language to retrieve compressed AI memory from past sessions.

Instructions

Decompress Engram Shorthand (ES) back to natural language.

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": {
      "text": "<text>"
    },
    "name": "engram_decompress"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It doesn't state that this is a stateless/non-mutating transform, nor what happens on malformed or non-ES input, nor any size limits — all of which matter for an inverse-decoding tool.

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?

A single tight sentence with the verb and resource front-loaded; nothing superfluous.

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?

For a one-parameter tool with no annotations or output schema, it does state the output type (natural language), but failure modes, input validity requirements, and its relationship to engram_compress are absent.

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 coverage is 0% and the single 'text' parameter is undocumented. The description's reference to 'ES' implies the input should be Engram Shorthand, but it never ties that to the parameter or describes acceptable formats, so it only partially compensates.

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?

Names a specific verb ('Decompress') and a specific resource ('Engram Shorthand (ES)'), and clarifies the output form ('back to natural language'). It doesn't explicitly cite the inverse sibling engram_compress, but the phrasing makes the inverse relationship inferable.

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 statement of when to use this instead of engram_compress or any other sibling, and no preconditions (e.g., that the input must be valid ES). Usage is only implied by the verb.

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