Skip to main content
Glama

get_timeline

Retrieve the decision timeline for a project to track architectural decisions and their evolution over time.

Instructions

Get the decision timeline for a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNoProject name (omit for all projects)

Implementation Reference

  • Tool registration and handler implementation for 'get_timeline' in index.js.
    server.registerTool('get_timeline', {
      description: 'Get the decision timeline for a project',
      inputSchema: {
        project: z.string().optional().describe('Project name (omit for all projects)'),
      },
    }, async ({ project }) => {
      const timeline = getTimeline(project);
      if (!timeline.length) return { content: [{ type: 'text', text: 'No records found' }] };
    
      const output = timeline.map(t => {
        const commit = t.git_commit ? ` (${t.git_commit.slice(0, 7)})` : '';
        const adr = t.adr_id ? ` → ADR-${t.adr_id} [${t.status}] "${t.adr_title}"` : '';
        return `[${t.created_at}] ${t.project}${commit}${adr}\n  ${t.summary ?? 'no summary'}`;
      }).join('\n');
    
      return { content: [{ type: 'text', text: output }] };
    });
  • db.js:147-157 (handler)
    Database function implementation for 'getTimeline' that fetches the timeline records from the database.
    export function getTimeline(project) {
      const where = project ? 'WHERE s.project = ?' : '';
      const params = project ? [project] : [];
      return db.prepare(`
        SELECT s.id, s.project, s.summary, s.git_commit, s.created_at,
               a.id as adr_id, a.title as adr_title, a.status
        FROM sessions s LEFT JOIN adrs a ON a.session_id = s.id
        ${where}
        ORDER BY s.created_at ASC
      `).all(...params);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get' but doesn't clarify if this is a read-only operation, what permissions are needed, how data is returned, or any rate limits. For a tool with no annotations, this is a significant gap in transparency.

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, efficient sentence with zero waste. It's front-loaded and appropriately sized for the tool's apparent simplicity, making it easy to parse quickly.

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 no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what a 'decision timeline' entails, how results are structured, or any behavioral traits, leaving the agent with insufficient context to use the tool effectively beyond basic invocation.

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 schema description coverage is 100%, with the parameter 'project' documented as 'Project name (omit for all projects)'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating further.

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 clearly states the action ('Get') and resource ('decision timeline for a project'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'search_decisions' or 'get_adr_graph', which might also retrieve decision-related information, so it lacks sibling distinction.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage based on the name alone, which is insufficient for effective tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wooxogh/adr-mcp-setup'

If you have feedback or need assistance with the MCP directory API, please join our Discord server