Skip to main content
Glama

diff_functions

Read-onlyIdempotent

Lists functions changed in a git diff against a specified ref (default HEAD) to check before review or commit.

Instructions

Functions changed in the git diff against a ref (default HEAD), to check before review or commit.

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": "diff_functions"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoList everything instead of stopping at 200 items.
refNoGit ref, e.g. HEAD~3 or main.HEAD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only a workflow hint ('before review or commit') and does not describe what is returned or how the diff scope is resolved.

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 compact sentence with the core resource front-loaded and the ref default folded in parenthetically. No filler, though the sentence is grammatically a fragment rather than a directed statement.

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

Completeness3/5

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

For a simple two-optional-parameter read tool with no output schema, the definition covers the what and a hint of when. It stops short of indicating the shape of the result (function names, file locations, diff hunks), which an agent would need since no output schema exists.

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%, so both the 'ref' and 'all' parameters are already documented, including the HEAD default. The description repeats the HEAD default and adds nothing about ref syntax or the 200-item cap beyond what the schema states.

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 resource — functions changed in a git diff against a ref — which is clearly distinguishable from sibling tools like find_function, usages, or analyze. It lacks an explicit verb ('List'/'Return'), reading as a noun phrase, but the intent is unambiguous.

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?

The phrase 'to check before review or commit' implies a usage context, but it never says when to prefer this over alternatives, nor when not to use it. An agent can infer intent but gets no routing guidance.

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