Skip to main content
Glama

File history

code_history
Read-only

A file's revisions, newest first, following it through moves; each names its change, who made it and why.

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": {
      "path": "<path>",
      "org": "<org>"
    },
    "name": "code_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose trees and sites to use. Required on every call, even when only one organization is listed; a path never names it.
pathYesThe file's address, <tree>:<path>.
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description is not burdened with safety details. It still adds genuinely new behavior: results are ordered newest first, history is carried across file moves/renames, and each entry carries the change name plus actor and rationale. It leaves pagination/limit behavior undisclosed, which keeps it from a 5.

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?

One dense sentence with no filler, and the most useful facts (what it returns, ordering, move-following) are front-loaded. The noun-phrase fragment style is efficient but slightly less scannable than a verb-led sentence.

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 read-only tool with no output schema and full annotation coverage, the description covers the essential return shape well. It omits the pagination/truncation story — a default of 20, max 50, and no mention of whether more revisions exist beyond that — which an agent needs before trusting the list as complete history.

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 67%, and the description adds no parameter-level guidance at all. It does not clarify that limit caps at 50 and defaults to 20, or that limiting is the only way to narrow output. With two of three parameters already well documented inline, a baseline 3 holds, but nothing compensates for the bare limit property.

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 the specific resource and its content: a file's revisions, newest first, tracked across moves, each with change name, author, and reason. That is far more informative than a title restatement. It stops short of a 5 because it never distinguishes this from sibling history tools (wiki_history, code_changes) — the read surface is clear, but the tool's niche is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use statement and no named alternative. An agent must infer that this is the per-file revision log and that wiki_history serves pages rather than code trees. The description gives no prerequisites, no error guidance (e.g. what a bad path yields), and no routing to code_changes for audit-style queries.

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