Skip to main content
Glama

memory_due

Read-only

Lists stored memories old enough to need re-confirmation with the person before reliance. Optionally measures age as of a given date, defaulting to now.

Instructions

List memories old enough that they should be re-confirmed with the person before being relied on.

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": "memory_due"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoISO date to measure age against. Default now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered and the bar is lower. The description adds the behavioral intent behind the filter (re-confirmation with the person), but leaves the actual selection rule opaque: no threshold, no indication of whether the cutoff is configurable, ordered, or bounded/paginated.

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 front-loaded sentence with zero filler; the purpose and the reason for the filter arrive immediately. It is efficient, though its brevity leaves the core selection rule unstated rather than clarified.

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 read-only tool with one optional parameter, no output schema, and annotations covering the safety profile, this is close to complete. The remaining gap is substantive rather than cosmetic: the agent cannot know what makes a memory "due," so it cannot predict result volume or set expectations for the user.

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

Parameters3/5

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

The single parameter is fully documented in the schema ("ISO date to measure age against. Default now."), so the schema does the heavy lifting. The description adds nothing about how as_of changes the result set or interacts with the undefined age threshold, so baseline 3 applies.

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 (memories) plus a distinguishing selection concept: memories old enough to warrant re-confirmation. An agent can tell this apart from a general memory_list. However, the operative criterion ("old enough") is never defined, and no sibling is named to sharpen the distinction.

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 phrasing "before being relied on" implies when to reach for this tool (verifying stale facts), which is real but indirect guidance. There is no explicit when-not guidance, no mention of memory_list or memory_recall as alternatives for unfiltered or relevance-based retrieval, and no statement of what happens if the caller ignores the result.

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

This server cannot be deployed

Other Tools