Skip to main content
Glama

Every saved version of a file

file_history
Read-onlyIdempotent

Every version of one file the registry has saved, newest first: label, date, grade and the sha256 of its exact bytes. Versions are kept by content hash, so a file that later changes or disappears on GitHub still has its history here.

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": {
      "ref": "<ref>"
    },
    "name": "file_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesowner/repo/name for a skill (anthropics/skills/pdf), owner/repo/path for any other file (vercel/next.js/AGENTS.md), or an art_ id from find_files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context, which it does: it discloses ordering ('newest first') and the content-hash retention model that explains why history survives upstream deletion. It stops short of stating whether results are paginated or capped.

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 with no filler: the resource, ordering and returned fields come first, and the retention rationale follows. Every clause carries information an agent would otherwise have to guess.

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 simple one-parameter read tool with no output schema, the description is nearly self-sufficient: it names the returned fields and their order. The remaining gap is volume behaviour — nothing says how many versions come back or whether there is a limit — which matters for a history listing.

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 single `ref` parameter's three accepted forms are fully documented in the schema. The description only adds 'one file', which reinforces that ref resolves to a single identifier rather than a pattern; that is a marginal addition over the schema, so the baseline of 3 applies.

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 (every saved version of one file) and its ordering (newest first), and enumerates what each version carries: label, date, grade, sha256. It does not explicitly contrast itself with siblings such as get_file or what_changed, so an agent must infer the split from the word 'version'.

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?

There is no explicit when-to-use clause and no named alternative, so guidance is only implied. The retention note ('a file that later changes or disappears on GitHub still has its history here') hints at the case where this beats fetching the current file, but the agent has to make that inference itself.

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