Skip to main content
Glama

What a branch changed

branch_changes
Read-onlyIdempotent

Lists records a branch added, changed, or deleted since a specified commit so you can review what a branch or proposal would bring to main. Use compare_record to inspect any single record.

Instructions

The records a branch inserted, updated or deleted since a commit, such as the commit it was made from: what a review round or a proposal would bring to main. Follow with compare_record for any one record.

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": {
      "branch": "<branch>",
      "since": "<since>"
    },
    "name": "branch_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceYesThe commit to compare from, such as main's latest commit when the branch was made.
branchYesThe branch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds useful scope context — the branch/commit comparison model and the intent of previewing a merge — but says nothing about ordering, grouping by change type, or result limits.

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 sentences, front-loaded with the core scope and followed by the single most useful routing hint. Nothing superfluous.

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

Completeness4/5

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

For a two-parameter read tool with annotations covering safety and no output schema, the description sufficiently conveys that the return value is the set of changed records. Minor gaps remain around pagination and whether changes are grouped by operation type.

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 100% and both parameters are documented in the schema, so the schema carries the load. The description only restates that 'since' is a commit reference, adding no semantics beyond what the schema already says.

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 the resource (records) and the precise scope (inserted, updated or deleted since a commit), which separates it from record_history and compare_record. The phrasing 'such as the commit it was made from' is grammatically tangled and slightly muddies the otherwise clear statement.

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

Usage Guidelines3/5

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

It gives a next-step pointer ('Follow with compare_record for any one record') and implies the use case (reviewing a round or proposal before merging to main), but it never states when not to use this versus alternatives like record_history or list_branches.

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