Skip to main content
Glama

MemBrowse

Commit memory summary

get_commit_summary
Read-only

For one commit, show every target's memory change against its base build: per region, the largest section and source-file changes, budget alerts, and, for targets with benchmark metrics, each metric's change. For a pull request, pass the PR's head commit SHA: its base is the tip of the PR's base branch, so the result is the whole PR's change. Use it to review a pull request or check whether a commit grew memory or moved a benchmark.

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>"
    },
    "name": "get_commit_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoThe commit: a full commit SHA, a SHA prefix (7+ characters), or a branch or tag name. Default: the head of the default branch. For a pull request, its head commit SHA.
limitNoSection, file and metric changes per target (default 10, max 200).
targetNoOnly this target (default: all).
projectYesThe project: a public project's GitHub 'owner/repo' (no API key needed), or, with an API key, a project id or name from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a read-only, non-destructive operation, so the description is not carrying the safety burden. It still adds real behavioral context beyond the schema: the comparison base for a PR head commit, that the result is the whole PR's change, and that per-target output covers regions, sections, files, alerts and metrics. Return shape and pagination/ordering behavior remain unspecified.

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?

The output content is front-loaded in the first sentence and the PR mechanics and use case follow in logical order. The prose is dense but each clause carries information; the only mild bloat is repeating the PR head SHA instruction that the ref schema already states.

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?

With no output schema, the description must convey what comes back, and it does: per-target, per-region changes, largest section and file changes, budget alerts, and per-metric benchmark changes. Combined with annotations and a fully documented schema, an agent has enough to call this correctly for both commit and PR review cases.

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 the schema already defines ref (SHA, prefix, branch/tag, default head of default branch, PR head SHA), limit, target and project. The description's only added meaning is the consequence of a PR head ref — that the base becomes the base branch tip — which is a minor increment on documented fields.

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?

"Show every target's memory change against its base build" gives a specific verb and resource and enumerates the payload: per-region changes, largest section and source-file deltas, budget alerts, and benchmark metric deltas. That implicitly separates it from history-style siblings such as get_memory_history and get_metric_history, but no sibling is named or contrasted explicitly.

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?

"Use it to review a pull request or check whether a commit grew memory or moved a benchmark" states the intended scenarios clearly, and the PR guidance specifies passing the head commit SHA because the base is the tip of the PR's base branch. No explicit when-not or named alternative is given, so it stops short of the top score.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources