Skip to main content
Glama
Sign In
Gantry

Gantry

by fourn9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_bot_memories

Read-only

Retrieve and inspect bot memories for a given session and role, with filters for time, intent, and basis to support debugging and context review.

Instructions

list bot 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": {
      "arguments": "<arguments>"
    },
    "name": "list_bot_memories"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.4.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing further—no note on pagination via 'limit'/'after', ordering, or scope by session—so it fails to exceed the annotation baseline.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is brief, but the brevity reflects under-specification rather than efficiency; there is no structure, scope statement, or distinguishing detail.

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

Completeness1/5

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

With a nested 2-parameter schema at 0% description coverage, no output schema, and a closely related sibling, the definition supplies none of the context an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the nested 'arguments' object contains opaque fields like 'basis', 'intent', 'role', 'after', and 'limit'. The description explains none of them, leaving critical inputs such as the required 'role' meaning undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"list bot memories" restates the tool name almost verbatim, adding only the verb 'list'. It does not explain what a 'bot memory' is or how this differs from the sibling list_persistent_memories.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no mention of prerequisites such as session_id scope, and no indication of when to prefer list_persistent_memories or bot_inbox instead.

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