Skip to main content
Glama
Sign In
chat-memory

chat-memory

by mav-rix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_recent

Fetch recently saved or updated memories to review recent context and changes in a project.

Instructions

Most recently saved or updated memories.

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_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only adds the notion of ordering by save/update time. It does not disclose default result size, ordering tie-breaks, whether the list is per-project or global, or any volume/rate behavior — the presence of an output schema only covers return shape, not these traits.

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?

The text is a single fragment with no wasted words, but it is under-specified rather than concise — it conveys a label, not an instruction, and lacks the structure (action + scope + constraints) an agent needs.

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

Completeness2/5

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

For a retrieval tool with two undocumented parameters and zero annotation coverage, the definition is too thin: return values are covered by the output schema, but param semantics, usage routing, and behavioral traits are all missing.

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

Parameters2/5

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

Schema description coverage is 0%, and the description never mentions the two parameters (limit, project) or their meaning, defaults, or valid ranges. It neither documents nor compensates for the undocumented schema.

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

Purpose3/5

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

The phrase 'Most recently saved or updated memories' identifies the resource (memories) and the ordering (recency), which hints at a listing operation, but it is a noun fragment with no verb and gives no differentiation from siblings such as recall or review. An agent can guess the intent but must infer that this is a list-style retrieval.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no statement of when to prefer this over recall, review, or get_memory, and no indication of prerequisites or exclusions. The agent must infer usage purely from the name.

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