Skip to main content
Glama

get_memory

Fetch a single memory by its exact slug identifier to get full details—why, when to apply, tags—after search returns a relevant slug.

Instructions

Fetch a single memory by its exact slug identifier. CALL THIS: when search_memories returned a relevant slug and you need the full details (why, when to apply, tags). Slugs are kebab-case identifiers like 'ig-pipeline-no-fallback' or 'trading-capital-track'.

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": "get_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe kebab-case memory slug (e.g. 'ig-pipeline-no-fallback')
formatNojson

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.14.3

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the result includes details such as why, when to apply, and tags, but it does not mention error behavior, missing slugs, permissions, or other operational constraints.

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?

Three short sentences, front-loaded with the core action and followed by a direct usage trigger and examples. There is no redundant or filler wording.

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 simple single-record fetch tool with no output schema, the description covers the essential call context: exact slug retrieval, when to use it after search, and the kind of detail returned. Minor gaps remain around the format parameter and error 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?

The description reinforces the slug parameter as an exact kebab-case identifier with examples, but the schema already documents that. It leaves the format parameter unexplained, including when to choose 'toon' versus the default 'json'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: fetch a single memory by exact slug. It also distinguishes this from search_memories by framing retrieval as the full-detail follow-up to a search result.

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?

It gives a clear trigger: call this when search_memories returned a relevant slug and full details are needed. It does not explicitly state when not to use it, but the alternative search path is named and contextualized.

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