Skip to main content
Glama

MemBrowse

Benchmark metric history

get_metric_history
Read-only

List a target's benchmarked commits, newest first, with each benchmark metric's value (cycle counts, timings, scores that CI attached) and its change from the previous commit that had the metric. Use it to see how a benchmark evolved and to find the commit that moved it; page back with 'offset'.

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

Input Schema

NameRequiredDescriptionDefault
refNoWhere to start: a full commit SHA, a SHA prefix (7+ characters), or a branch or tag name. Default: the head of the default branch.
limitNoCommits per page (default 30, max 200).
offsetNoCommits to skip, for paging (default 0).
targetYesTarget name (see list_targets).
metricsNoOnly these metrics (default: all of the target's metrics).
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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavior beyond that: results are ordered newest first, deltas are computed against the previous commit that actually had the metric (not simply the prior commit), and paging is offset-based.

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?

Two sentences, front-loaded with the resource and its contents, then the use case and paging note. Every clause carries information; the only mild cost is the dense parenthetical listing of metric value types.

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?

With no output schema, the description carries the burden of describing return values, and it does: an ordered list of commits with per-metric values and inter-commit deltas. Nothing essential is missing for a read-only listing tool, though the exact response envelope and behavior when no metrics exist are unstated.

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 description coverage is 100%, so ref, limit, offset, metrics, target and project are all documented in structured form, which sets the baseline at 3. The description only reinforces offset for paging and alludes to metric selection; it adds no format or edge-case detail beyond the schema.

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 gives a specific verb and resource ("List a target's benchmarked commits") plus exactly what each row carries: metric values and the change from the previous commit holding that metric. It is unambiguous on its own, but it never contrasts itself with the nearest sibling (get_memory_history) or with compare_builds, so the agent must infer the boundary.

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?

It states the intended use case explicitly: "see how a benchmark evolved and to find the commit that moved it," and adds the paging mechanic ("page back with 'offset'"). There is no when-not guidance and no named alternative for adjacent questions such as comparing two builds, which keeps it below a 5.

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