Fine Structure

List Agent Memories

list_agent_memories

Read-onlyIdempotent

What an agent has learned and kept: long-term facts and insights, newest first, optionally only those about one customer.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "list_agent_memories"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`agent_id`	Yes	The agent id, from list_agents.
`customer_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the provided annotations (readOnlyHint: true), the description provides critical behavioral traits, specifically that results are returned 'newest first.' This ordering is a functional behavior not captured elsewhere.

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?

The definition is extremely concise, conveying the data type, retrieval scope, and default ordering in two perfectly economical sentences. There is zero wasted 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?

The definition provides enough context regarding the data nature, scope (agent vs. customer), and retrieval order to allow an agent to call the tool correctly. It is highly complete for a list operation that lacks an explicit output schema.

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?

Given that schema description coverage is low (33%), the description adds essential meaning. It clarifies that 'customer_id' is a scoping mechanism ('optionally only those about one customer'), which is semantic information beyond the basic schema definition.

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 is highly specific, identifying the resource as agent memories and the content as 'long-term facts and insights.' It clearly distinguishes this memory retrieval function from general conversation or document listing tools in the sibling list.

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?

The description guides usage by defining the optional scope: filtering by 'one customer' is optional. This tells the agent how to differentiate between a global retrieval and a scoped query without needing to examine parameter requirements.

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

All Fine Structure tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?