Skip to main content
Glama

get_timeline

Fetch surrounding conversation turns around a given episode ID to review context before and after a specific memory episode.

Instructions

Fetch surrounding conversation turns around a given episode_id.

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": {
      "episode_id": "<episode_id>"
    },
    "name": "get_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
beforeNo
episode_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/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. It does not disclose ordering of returned turns, default window sizes, behavior at conversation boundaries, or whether reads have any cost or permission constraints, leaving key traits to guesswork.

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 no filler or redundancy. Its brevity is efficient, though it edges toward under-specification rather than tight completeness.

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?

The tool is simple and an output schema exists, so return values need not be explained. However, with zero schema coverage on two of three parameters and no annotations, the description omits information an agent needs to size the window correctly.

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 there are three parameters, yet the description explains only episode_id. The before and after window parameters — including their defaults of 3 — are never described, so the description fails to compensate for the schema gap.

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 verb (fetch) and a well-defined resource (surrounding conversation turns) anchored to episode_id. An agent can tell this retrieves context rather than searching, but it never names or contrasts with siblings like search_episodes, so differentiation is left implicit.

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?

Usage is only implied: 'surrounding conversation turns around a given episode_id' suggests it is the tool for expanding context after finding an episode. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative for narrower/wider retrieval.

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