Skip to main content
Glama

Revision

revision
Read-onlyIdempotent

Fetch one archived commit by its Software Heritage revision id (the 40-hex id, which for a git repository is the git commit sha). Returns the commit message, author and committer with their dates, the directory id of the tree it points at, and its parent commits. Accepts a bare hex id or a full SWHID ("swh:1:rev:"). Because the archive is content-addressed, this keeps resolving after the repository it came from has been renamed, moved or deleted. Sourced from the Software Heritage archive.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
idYesRevision id, a 40-character hex sha ("309cf37fe2a781279b7675d4bb7173198e532867") or a SWHID ("swh:1:rev:309cf37f...").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Revision id — a 40-character hex sha (\"309cf37fe2a781279b7675d4bb7173198e532867\") or a SWHID (\"swh:1:rev:309cf37f…\")."New value: +"Revision id, a 40-character hex sha (\"309cf37fe2a781279b7675d4bb7173198e532867\") or a SWHID (\"swh:1:rev:309cf37f...\")."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the bar is lower, and the description still adds real value: it enumerates the returned fields (message, author/committer with dates, directory id, parent commits) and explains the archive's content-addressing guarantee. It stops short of stating failure behavior for an unknown or malformed id, which is the one remaining gap.

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?

Four sentences, front-loaded with the core action, then the return shape, then accepted id formats, then the durability rationale. Nothing is padding; each sentence carries distinct information.

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?

For a single-parameter lookup with no output schema, the description supplies the return fields inline, the accepted input formats, and the semantic meaning of the result. There is nothing material an agent would need before calling it that is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes slightly beyond the schema by mapping the 40-hex id to 'the git commit sha' for git repositories, which helps an agent translate a value from another tool. The dual-format acceptance is repeated from the schema rather than newly added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource pair ('Fetch one archived commit') scoped to a named identifier system (Software Heritage revision id), which immediately distinguishes it from siblings like origin_search or origin_visits. It also disambiguates the id form, so an agent knows exactly which resource is being retrieved.

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?

Usage is implied rather than stated: the agent must infer it should call this when it already has a revision id. The content-addressed persistence note gives a genuine reason to prefer this over a live git lookup, but no sibling is named and no exclusion condition ('use X instead if you only have a repo name') is offered.

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.