Skip to main content
Glama
Sign In
PLUR

PLUR

Official
by plur-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

plur_timeline

Read-onlyIdempotent

Retrieve past episode records by filtering the timeline with time range, agent, channel, or full-text search.

Instructions

Query the episodic timeline — retrieve past episodes filtered by time, agent, or search

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

Input Schema

NameRequiredDescriptionDefault
agentNoFilter by agent identifier
sinceNoISO date string — only episodes after this time
untilNoISO date string — only episodes before this time
searchNoFull-text search within episode summaries
channelNoFilter by channel

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.14.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows this is a safe, idempotent query. The description echoes 'Query' and 'retrieve', which aligns but adds no new behavioral context (e.g., pagination, data freshness, or scope). With annotations covering safety, a score of 3 is appropriate.

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 a single sentence that front-loads the action ('Query the episodic timeline') and then elaborates on filters. Every word is needed; no fluff. Extremely concise.

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 has 5 optional parameters, no output schema, and no nested objects. The description explains the filtering capability but does not mention the output format or any limitations like pagination. Given the lack of output schema, the description could be more complete. However, annotations cover safety, so it's adequate but not full.

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?

Schema description coverage is 100% for all 5 parameters, so the schema already explains each parameter. The description does not add additional semantics or examples beyond what the schema provides. Baseline score of 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Query the episodic timeline — retrieve past episodes filtered by time, agent, or search'. The verb 'Query' and resource 'episodic timeline' are specific. Among sibling tools like plur_recall, plur_history, etc., this tool is uniquely positioned as a timeline filter query, so it distinguishes well.

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 filtered episodes but does not explicitly state when to use this tool versus alternatives (e.g., plur_recall, plur_history). No guidance on when not to use it or prerequisites. Usage context is hinted but not fully specified.

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