Skip to main content
Glama

read_memory

Returns one memory by slug, including its body, links, and backlinks, so agents can inspect shared context.

Instructions

Read one memory by slug, with its body, links and backlinks.

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": {
      "slug": "<slug>"
    },
    "name": "read_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 behavioral burden. It helpfully discloses the return shape (body, links, backlinks), which implies a read-only operation, but says nothing about behavior on a missing or invalid slug, permission requirements, or whether the read is scoped to a connection/workspace.

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?

A single front-loaded sentence with no filler, and the returned fields are appended compactly. It could be marginally tighter but nothing is wasted.

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 lookup tool with no output schema, the description reasonably covers what the call does and what comes back (body, links, backlinks). The notable remaining gap is error/not-found behavior, which matters for a keyed fetch.

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%, so the single parameter is documented only by its pattern and length constraints. The phrase 'by slug' adds the key insight that slug is a human-readable identifier used for exact lookup, but the description does not explain slug provenance, formatting, or case behavior beyond what the regex already enforces.

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 memory) plus the lookup key (slug) and the payload returned (body, links, backlinks). The word 'one' signals a single-item fetch rather than a list, which separates it from search/list siblings, though no sibling is named explicitly.

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: read a single memory when you already have its slug. There is no explicit when-to-use, when-not, or pointer to alternatives like search_context or read_skill for other resource types, so the agent must infer routing.

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