Skip to main content
Glama
Sign In

MemScope

by ai.memscope
OverviewDiscussionsAdmin

Get memory

get_memory
Read-onlyIdempotent

Use this when you need one memory in full, by an id from search_memories or list_memories (for example before changing it): content, scope, sensitivity, review state and version history, with a version's content only where policy lets the person read it. Not for searching (use search_memories).

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
memory_idYesMemory id ('mem_' prefix optional).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real value: it discloses that version content is only returned 'where policy lets the person read it', warning the agent that results may be partially redacted. It does not say what happens for an unknown or inaccessible id, which is the main remaining gap.

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?

One compact sentence front-loads the when-to-use condition, then adds the input source, the returned facets, and the exclusion. Every clause carries distinct information and nothing is repeated from the annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with full schema coverage, an output schema, and rich annotations, the description covers purpose, input provenance, return facets, policy-based redaction, and the alternative tool. Nothing an agent needs to call it correctly is missing.

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 100% and the single parameter is documented, including the optional 'mem_' prefix, so the baseline is 3. The description adds meaning beyond the schema by specifying where a valid id comes from (`search_memories` or `list_memories`), which prevents the agent from fabricating identifiers.

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?

States a specific verb and resource ('need one memory in full, by an id') and enumerates the returned facets (content, scope, sensitivity, review state, version history). It also explicitly excludes searching and names the sibling to use instead, so the agent can distinguish it from `search_memories` without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('when you need one memory in full'), a concrete scenario ('for example before changing it'), and the provenance of the required input (an id from `search_memories` or `list_memories`). It closes with an explicit when-not clause routing search intent to `search_memories`.

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

All MemScope 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