Skip to main content
Glama
anaknegeri

agent-session

by anaknegeri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

memory.get

Read-only

Retrieve one long-term knowledge entry by ID as JSON from agent-session; it errors when the ID does not exist, so search by topic first if the ID is unknown.

Instructions

Return one long-term knowledge entry by ID as JSON (id, kind, content, source_type, source_id, session_id, agent, created_at). Read-only. Errors when the ID does not exist. Use memory.search when you only know the topic.

Input Schema

NameRequiredDescriptionDefault
memory_idYesKnowledge ID (mem_...), from memory.search or memory.put

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.9
    • changedInput schema / properties / memory_id / description
      Previous value: -"Knowledge ID"New value: +"Knowledge ID (mem_...), from memory.search or memory.put"
  2. First observedv0.1.8

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces read-only behavior while adding useful error semantics (errors when ID does not exist) and the returned field set. It does not discuss auth or rate limits, but those are not central for a simple read.

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 compact sentences, front-loaded with the core action and return shape, followed by safety and alternative guidance. No wasted text.

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?

Complete for a single-parameter read tool: it covers purpose, return fields, read-only nature, error condition, and the alternative when only a topic is known. No output schema exists, so naming return fields is sufficient.

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 the memory_id parameter is already fully documented, including its mem_... format and source. The description adds little parameter-level detail beyond 'by ID,' which is appropriate given 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: returns one long-term knowledge entry by ID. Explicitly distinguishes itself from memory.search by noting the lookup-by-ID vs topic-search distinction.

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 a clear when-to-use alternative: 'Use memory.search when you only know the topic.' This directly routes the agent between sibling tools.

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

Deploy Server

Other Tools