Skip to main content
Glama

project_timeline

Review a project's activity history newest first, including agent firings, triggered runs, and recorded findings, to track what happened and when.

Instructions

What happened in the project, newest first: each firing with the runs it woke and their findings, and the findings recorded without a firing (external agents' among them).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

B3.1/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, and it does disclose real behavior: results are ordered newest first and the payload interleaves firings, spawned runs, and unattributed findings from external agents. It says nothing about access requirements, whether the history is truncated by the limit default of 20, or whether empty projects return an empty list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, and the ordering fact comes early. However, it is dense and hard to parse, stacking two 'findings' clauses and a parenthetical, and it relies on unexplained domain jargon (firing, run) that an unfamiliar agent cannot resolve.

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?

An output schema exists, so return values need not be described, which the description correctly leaves alone. What remains missing for a two-parameter read tool is the meaning of 'limit' and the empty-string project default, plus any note on access scope.

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 0% for two parameters, so the description would need to compensate; it only obliquely indicates that results are scoped to a project, and never explains 'limit' or the empty-string default for 'project'. The baseline for adequate-but-thin coverage applies, though the 'limit' behavior is a genuine 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 names a concrete resource and its shape: a project's chronological history, newest first, composed of firings, the runs they woke, and standalone findings. That is specific enough to distinguish a history feed from state or settings tools, but it never states an explicit verb (list/retrieve) and gives no hint about how it differs from siblings like how_is_project.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no named alternative; the agent must infer that this is for reviewing past activity. The phrase 'What happened in the project' only weakly implies the use case, and nothing indicates what to call instead when the agent wants current status.

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