Skip to main content
Glama

repo_changes

Read-onlyIdempotent

Display recently indexed commits and changed files to help coding agents identify what changed in a repository.

Instructions

Show the latest indexed commits and changed files.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "repo_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.6

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the meaningful hint that results come from an index, implying they may lag the repository, but says nothing about ordering, default result count, or pagination behavior.

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?

A single front-loaded sentence with no filler, and the key qualifier 'indexed' is placed before the resource. It is efficient, though arguably so sparse that it borders on under-specification rather than true concision.

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?

With no output schema, the description should describe the return shape, and it only loosely does by naming commits and changed files. It omits the meaning of 'latest' (how many, in what order), the limit default, and any indication of how commits are structured in the response.

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

Parameters2/5

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

The single 'limit' parameter has 0% schema description coverage and is not mentioned in the description at all, so its meaning, default, and maximum are nowhere defined. With only one parameter and no compensating text, the agent cannot tell what happens if limit is omitted or how large it may be.

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 a specific verb and resource: showing the latest indexed commits plus the files each commit changed. The word 'indexed' usefully scopes the data source. It does not distinguish itself from plausible siblings such as repo_history, leaving the agent to guess which one returns commit history.

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?

There is no statement of when to use this versus repo_history or repo_search, and no exclusions or prerequisites. The agent must infer usage purely from the phrase 'latest indexed commits'.

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