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

agent-memory-sqlite

by Urthella
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remember

Save durable facts, decisions, or conventions for future sessions; resubmitting the same text refreshes the stored entry instead of creating duplicates.

Instructions

Save a durable fact, decision or convention for future sessions. Saving the same text again refreshes it instead of duplicating.

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": {
      "content": "<content>"
    },
    "name": "remember"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose a key behavioral trait — re-saving identical text refreshes rather than duplicates, i.e. upsert semantics. It omits permissions, storage limits, and return feedback for the save, so disclosure is partial.

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?

Two tight sentences with the core purpose front-loaded and a useful dedupe caveat as the second line. Nothing is wasted or buried.

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

Completeness3/5

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

For a simple 3-param tool with no annotations or output schema, the description covers purpose and upsert behavior adequately. It falls short on parameter guidance (tags, content semantics) that nothing else in the structured data supplies.

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 coverage is only 33% (only 'project' is documented in the schema). The description says 'same text' which hints that content is the fact text, but gives no meaning for 'tags' or how content is matched for refresh, leaving two of three parameters under-explained.

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 (save) and resource (durable fact, decision or convention), with the 'future sessions' scope making clear it is a persistence tool. It implicitly contrasts with the read-oriented siblings (recall, recent) but never names them explicitly.

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?

Implies usage via 'durable fact, decision or convention for future sessions', which tells the agent to use this for lasting knowledge rather than transient state. However, it never states when NOT to use it or points to siblings like recall/forget for other operations.

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