Skip to main content
Glama
Sign In
agent-memory-sqlite

agent-memory-sqlite

by Urthella
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

recent

Read-only

Lists saved or refreshed memories in reverse chronological order, with optional project and limit filters.

Instructions

List the most recently saved or refreshed 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": "recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
projectNoProject name. Defaults to "app". Use "*" for all projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, and the description adds that results are ordered by recency of save/refresh, which is useful context beyond annotations. However it does not disclose sort direction, pagination, or whether 'refreshed' changes ordering, leaving the return behavior underspecified.

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

Conciseness4/5

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

A single efficient sentence with no padding, front-loading the action and the ordering concept. It is appropriately sized but so short that it omits needed detail.

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?

With no output schema, the description should clarify ordering, default limit, and scope defaults, but it covers none of these. An agent cannot tell how many results to expect, what order they arrive in, or how 'limit' behaves, making it incomplete for a filtered-list tool.

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 50%: the 'project' param is documented (default 'app', '*' for all) but 'limit' has no description and no stated maximum of 50. The description adds nothing about either parameter, so it fails to compensate for the coverage gap on 'limit'.

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?

States a specific verb (List) and resource (most recently saved or refreshed memories), which tells the agent this is a recency-ordered browse rather than a search. It does not name or distinguish itself from the sibling 'recall', which is the closest alternative, so it stops short of a 5.

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?

The phrase 'most recently saved or refreshed' implies a browsing/latest-activity use case, but there is no explicit statement of when to prefer this over 'recall' (search) or when not to use it. Usage must be inferred from the name and siblings.

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