Skip to main content
Glama

timeline

Retrieve the git commit history for an entity to see document changes over time. Use this to determine what was true at a specific point in time.

Instructions

Return the git history of the document that holds an entity. Read-only.

    Resolves ``entity_id`` to a file via frontmatter ``id:`` field, then
    runs ``git log`` for that file. Use this to answer "what was true at
    time T?" — Git history is the validity window; no separate
    ``valid_from``/``valid_to`` columns are stored.

    Args:
        entity_id: Frontmatter ``id`` value of the entity
        limit: Max commits to return (default 20, max 200)
        project: Target project name (optional)

    Returns:
        Newest-first list of commits with short hash, ISO date, author,
        and subject. Empty result hints if the docs repo is not a git
        checkout or the file has no history.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
projectNo
entity_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description details the read-only nature, the resolution logic, git log execution, return format, and error hints (empty result for non-git checkout). It adds substantial behavioral context beyond annotations (none provided).

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 concise with a clear summary, structured Args/Returns sections, and each sentence adds value. No wasted words.

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

Completeness5/5

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

Given the output schema exists, the description covers the return format and error cases. It explains the tool's purpose, parameters, and behavior comprehensively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description explains all three parameters: entity_id (frontmatter id), limit (max commits, default 20, max 200), and project (optional). This adds meaning beyond the bare schema.

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 returns git history for a document, using a specific verb (Return) and resource (git history of the document). It distinguishes from siblings by focusing on historical timeline, unlike search or write tools.

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?

The description explicitly provides a use case: 'Use this to answer "what was true at time T?"' and explains why git history is used. It does not explicitly mention when not to use or name alternatives, but the context is clear.

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/dl4rce/flaiwheel'

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