Skip to main content
Glama
Sign In
PMI

PMI

by yunzePlaud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_get

Read-only

Retrieve memories, sources, entities, or proposals by ID; include version history and paged source text to support AI agent long-term memory lookup and review.

Instructions

Fetch memories (mem_), sources (src_, full text paged by text_offset/text_limit), entities (ent_) or proposals (prp_) by id. include_history adds a memory's version history.

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": {
      "ids": "<ids>"
    },
    "name": "memory_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
text_limitNo
text_offsetNo
include_historyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, so safety is covered. The description adds genuine behavioral detail beyond that: source records return full text that is paged, and include_history enriches a memory with version history. It does not cover behavior for unknown prefixes or missing ids, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with the verb and the id-prefix map, with no filler. The parenthetical prefix list is compact but slightly cryptic for a first-time reader.

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?

An output schema exists, so return values need not be described, and the description covers the id formats and the two non-obvious parameters. What remains is edge-case behavior, which is a smaller omission than the core guidance it does provide.

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 description coverage, the description must carry parameter meaning, and it largely does: text_offset/text_limit are tied to paging of source full text, include_history is explained as version history, and ids are explained through the prefix taxonomy. Remaining gaps are minor, such as whether paging affects non-source records.

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 uses a specific verb ("Fetch") plus the exact resource classes and their id prefixes (mem_, src_, ent_, prp_), which tells an agent precisely what can be retrieved. It implicitly separates id-based lookup from siblings like memory_search and memory_list, though it never names them.

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?

"by id" signals that this is direct lookup rather than search or listing, which is usable context. However, there is no explicit statement of when to prefer this over memory_search or memory_list, and no prerequisites or failure conditions are given.

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