Skip to main content
Glama
Sign In
Longhand

Longhand

by Wynelson94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_project_timeline

Retrieves a timeline of recent project sessions with their outcomes (shipped, fixed, stuck, exploratory) for a quick project status overview.

Instructions

Session-level timeline for a project. Returns recent sessions with their outcomes (shipped / fixed / stuck / exploratory) for a bird's-eye view of what's been happening in a project lately.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_project_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 50)
sinceNo
untilNo
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states it returns sessions with outcomes but doesn't disclose read-only nature, ordering, or side effects.

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?

Two efficient sentences, front-loaded with purpose, no wasted words.

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

Completeness2/5

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

Given 4 parameters, no output schema, and many siblings, the description is too brief. It omits parameter details, ordering, and structure of the timeline.

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 coverage is 25% (only limit described). Description adds meaning to since/until as date filters and project_id as identifier, but lacks format details.

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 it returns a session-level timeline with specific outcomes (shipped/fixed/stuck/exploratory), distinguishing it from siblings like list_sessions or get_session_timeline.

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

Usage Guidelines4/5

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

It implies use for a bird's-eye view of recent project activity, providing context but lacking explicit when-not-to-use or alternative comparisons.

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