Skip to main content
Glama

list_agent_memory

Read-only

List Otto/Now Assist AI agent long-term memory entries by user, type, category, or active status to inspect stored semantic and episodic memories.

Instructions

List Otto / Now Assist AI agent long-term memory entries (sn_aia_memory): semantic and episodic memories stored per user, with category, relevance score and source record.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_agent_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoMemory type
userNosys_user sys_id or user_name
limitNoMax records (default 50)
activeNoFilter on active (default: all)
categoryNoLong-term memory category sys_id (sn_aia_ltm_category)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish that this is a non-mutating read, so the description does not need to restate safety. It adds useful context by identifying the underlying table and clarifying that memories are stored per user with category, relevance score, and source record, but says nothing about pagination behavior, ordering, or volume of results.

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?

It is a single front-loaded sentence that identifies the resource, the backing table, and the payload contents with no filler. Every clause carries information an agent can use.

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 read-only list tool with five optional, fully documented parameters and no output schema, the definition covers what is needed to call it correctly. A brief note on result ordering or default scope would close the remaining gap, but nothing essential is missing.

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 description coverage is 100%, so all five optional filters (type, user, limit, active, category) are already documented with defaults and enum values. The description echoes the per-user and category concepts but adds no syntax, format, or interaction details beyond the schema, making the baseline 3 appropriate.

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?

The description names a specific verb and resource ('List Otto / Now Assist AI agent long-term memory entries'), gives the backing table (sn_aia_memory), and enumerates the kind of data returned (semantic/episodic memories, category, relevance, source record). The resource is plainly distinct from siblings such as list_agent_tools or list_agent_evaluations, though it never explicitly contrasts itself with any of 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 by the tool's name and the data it exposes; there is no statement of when to choose this over another listing tool, no prerequisites, and no exclusions. An agent can infer 'call this to inspect an agent's stored memories', but nothing more is offered.

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