Skip to main content
Glama

rr_get_memory_entry

Read-onlyIdempotent

Read one saved memory entry by namespace and key to reuse stored context; expired entries are excluded, and the namespace must be admin-granted.

Instructions

Read one saved memory entry by namespace and key. Expired entries are not returned. The namespace must have been granted to this API key by an admin.

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": {
      "namespace": "<namespace>",
      "key": "<key>"
    },
    "name": "rr_get_memory_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe entry's key within the namespace, up to 200 characters.
namespaceYesA context namespace this key has been granted, for example supplier_rules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A4/5.0
Behavior4/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 two genuinely new behavioral facts: expired entries are silently excluded from results, and access requires an admin-granted namespace. It stops short of describing what a missing/expired key returns.

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, each carrying distinct information: identity of the operation, expiry behavior, and access prerequisite. Front-loaded with the operation and free of filler.

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 two-parameter read tool with full schema coverage and an existing read-only annotation set, this is nearly complete: lookup semantics, expiry filtering and auth prerequisite are all stated. The one gap is the absence of an output schema combined with no mention of what a successful response contains.

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 100%, so both parameters are already documented, including the 'granted namespace' wording and the supplier_rules example. The description's restatement of the namespace grant requirement adds emphasis but no new syntax, format, or constraint information beyond the schema.

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 with its lookup axes: 'Read one saved memory entry by namespace and key.' The singular 'one' plus the key-based lookup distinguishes it from rr_list_memory_entries, rr_save_memory_entry and rr_delete_memory_entry without needing to name 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?

Usage is only implied: an agent can infer this is the fetch-a-known-entry tool, and the prerequisites (granted namespace, non-expired) narrow the valid case. There is no explicit statement of when to prefer this over rr_list_memory_entries for discovery, or what to do when the entry is missing.

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