Skip to main content
Glama
Sign In

Pryzm Memory

by com.pryzm-memory
OverviewDiscussionsAdmin

Get memories by ID

memory_get
Read-onlyIdempotent

Returns the full content of saved memories by id (up to 20 ids). Meant for results whose excerpt is truncated.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the 20-id batch ceiling, which is real operational context, but says nothing about behavior with unknown or deleted ids, ordering of results, or partial failures. With annotations carrying the safety semantics, a 3 is appropriate.

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 with zero waste, and the core behavior is front-loaded ahead of the usage hint. Nothing is repeated from the title.

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 one-parameter read tool with a full annotation set and no output schema, the definition covers purpose, batch limit, and use case. Only edge-case behavior for missing ids is left undisclosed, which is a minor gap at this complexity level.

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 0% and the single 'ids' array has no description, so the description must compensate. It does: 'by id (up to 20 ids)' explains that the parameter is a batch of identifiers and caps the batch size, which the schema alone does not convey.

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 and resource: returns full content of saved memories by id, with the batch cap stated inline. The phrase 'by id' implicitly distinguishes it from the search/list siblings, but no sibling is named as an alternative.

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?

'Meant for results whose excerpt is truncated' gives a clear triggering condition and implies the search-then-hydrate flow. It does not say when not to use it (e.g., when the excerpt is already complete) or name memory_search as the retrieval path.

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

All Pryzm Memory toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources