Skip to main content
Glama

list_history

Read-onlyIdempotent

Retrieve a project branch's newest-first history, including pushes, commits, rebuilds, and stage moves for tracking and audit purposes.

Instructions

List the history of a branch of a project, newest first: each push with its commits, each rebuild and each move between stages.

Returns: the events, each with its kind, date, pusher, commits, stages and the number, status and result of the build it made, and truncated, true when there are more. Touches: reads only Bounds: two requests to Odoo.sh, then one for each 20 of limit + 1 events, eight in all at most, the pages within 60 seconds; limit events, 10 by default and 100 at most.

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": "<project>",
      "branch": "<branch>"
    },
    "name": "list_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
branchYes
projectYes

Output Schema

NameRequiredDescriptionDefault
eventsYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • changedOutput schema / $defs / TrackedBuild / description
      Previous value: -"The build an event of a branch's history made, as it is now. `Client.build` has the rest of it."New value: +"A build as a summary gives it: its number, status and result, for an event of a branch's history or a\nbranch's last build. `Client.build` has the rest of it."
  2. Addedv0.6.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the exact request budget (two to Odoo.sh, then one per 20 of limit+1 events, eight max), a 60-second page window, the default and maximum limit, and the `truncated` flag that signals more results exist. Those are concrete cost and pagination facts an agent cannot get from readOnlyHint/idempotentHint alone.

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

Conciseness4/5

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

Front-loaded with the purpose, then explicitly labeled Returns/Touches/Bounds sections — every sentence carries information. The bounds sentence is dense and slightly hard to parse on first read, which is the only thing keeping it off a 5.

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?

Covers purpose, event shape, read-only nature, rate/request budget, page timeout, limit bounds, and truncation signaling. Even though an output schema exists, the description still tells the agent what fields each event carries, leaving nothing an agent needs in order to call it correctly.

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%, so the description has to carry the load, and it does for the non-obvious parameter: `limit` gets a default of 10, a ceiling of 100, and its role in the request-count formula. `project` and `branch` are only implied by "a branch of a project", but their meaning is self-evident from the names.

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?

States a specific verb and resource ("List the history of a branch of a project") plus the ordering ("newest first") and the exact event kinds included: pushes with commits, rebuilds, stage moves. That enumeration distinguishes it cleanly from list_builds and list_audit_log without the agent needing to open any schema.

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 event-kind enumeration gives clear context for when this feed is the right call rather than list_builds or list_audit_log, and "reads only" sets the safety expectation. It stops short of naming an explicit alternative or stating exclusions, so it is clear context without routing rules.

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