Skip to main content
Glama
Sign In
brain-engine

brain-engine

by LiorHalfon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_memory

Retrieve one stored memory by ID and page large entries with offset and max_chars to prevent context bloat.

Instructions

Read one source memory. Large memories are paged to avoid context bloat.

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": {
      "memory_id": "<memory_id>"
    },
    "name": "get_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNo
max_charsNo
memory_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a genuinely useful behavioral trait — that large memories are paged and why (context bloat) — but omits whether the read is side-effect free, how truncation is signalled, whether total length is returned, and what happens on an invalid id.

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 short sentences, zero filler, with the core action front-loaded and the paging caveat immediately after. Nothing could be removed without losing information.

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 simple single-record read with no output schema, the essentials are present, but the paging mechanic it advertises is under-specified — an agent cannot tell from this text whether a response is truncated or how to page through to completion. That gap matters precisely because the description raises paging as the key behavior.

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 0%, so all three parameters are undocumented in the schema. The description conceptually covers offset/max_chars via 'paged' and memory_id via 'one source memory', but it never binds to the parameter names, never explains units/defaults (max_chars=8000), and never says how a caller detects that more content remains.

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?

States a specific verb and resource ('Read one source memory'), which separates it from search_memory (find) and edit_memory/correct_memory (mutate). It does not name a sibling explicitly, so the differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Usage is only implied: 'one source memory' hints that the caller must already have a memory_id, presumably obtained from search_memory first. There is no explicit when-to-use/when-not guidance, no prerequisites, and no note on what to do if the id is unknown.

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