Skip to main content
Glama
Sign In
Vestige

Vestige

by samvallad33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

memory_timeline

Browse memories chronologically within any date range, grouped by day. Filter by tags, node type, or detail level to find exactly what you need.

Instructions

Browse memories chronologically. Returns memories in a time range, grouped by day. Defaults to last 7 days.

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

Input Schema

NameRequiredDescriptionDefault
endNoEnd of time range (ISO 8601 date or datetime). Default: now.
tagsNoFilter by tags (ANY match)
limitNoMaximum number of memories to return (default: 50, max: 200)
startNoStart of time range (ISO 8601 date or datetime). Default: 7 days ago.
node_typeNoFilter by node type (e.g. 'fact', 'concept', 'decision')
detail_levelNoLevel of detail: 'brief', 'summary' (default), or 'full'summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.0
  2. Removedv2.3.0
  3. First observedv2.1.27

TDQS

A3.6/5.0
Behavior3/5

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

Without annotations, the description carries the full burden. It discloses meaningful behavior: chronological ordering, day grouping, and the default 7-day window. However, it omits details like whether the operation is read-only, how pagination works beyond 'limit', and what values appear in the returned day groups.

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?

The description is two sentences, with the primary purpose front-loaded and the second sentence adding key behavioral context. Every clause contributes meaning and there is no redundancy or filler.

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

Completeness4/5

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

For a simple browse-with-filters tool, the description is nearly complete: it states the action, time-range behavior, grouping, and defaults. It lacks explicit sibling routing and a note about the shape of the returned day groups, but this is not a severe gap given the exhaustive schema.

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 input schema already describes all 6 parameters with 100% coverage. The description adds little beyond restating that memories are returned in a time range and defaults to 7 days, which the schema documents via 'start' and 'end' defaults. With full schema coverage, a baseline of 3 is appropriate.

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?

The description states a specific action ('Browse memories chronologically') and a clear resource with defined behavior. It differentiates itself from memory search by focusing on chronological browsing, though it doesn't explicitly name a sibling alternative.

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 description implies usage for retrieving memories in a time range and defaults to last 7 days, making the general use case clear. However, it does not provide explicit guidance on when to prefer this tool over the sibling 'search' tool or any exclusions.

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