Skip to main content
Glama

Entry history

get_entry_history
Read-only

An entry’s public edit history, newest first (next_offset pages on). A merged entry’s key gives its own history.

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": {
      "entry": "<entry>"
    },
    "name": "get_entry_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryYesThe entry: its VHID (11 digits), its short name (as in verifiedhandles.org/<short>), or its Wikidata QID (Q42).
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
vhidYesThe entry’s VHID: 11 digits, permanent.
limitYesThe page size used: the `limit` asked for, clamped to the endpoint’s range.
offsetYesThe offset used: the `offset` asked for, clamped to 0–10,000.
historyYesNewest first.
merged_intoNoPresent when the entry was merged into another: that entry’s VHID. The history is still the merged entry’s own.
next_offsetYesThe `offset` of the next page, or null when this is the last one. Follow it rather than computing it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / history / items / properties / actor_id
      Added value: +{
      +  "description": "An opaque id for this person, the same wherever they are named, for blocking; null whenever their name isn’t shown to you. Not an account id and can’t be turned into one; may change if the site’s keys are rotated.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / history / items / properties / proposer_id
      Added value: +{
      +  "description": "An opaque id for this person, the same wherever they are named, for blocking; null whenever their name isn’t shown to you. Not an account id and can’t be turned into one; may change if the site’s keys are rotated.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / history / items / required
      Previous value: -[
      -  "ref_id",
      -  "kind",
      -  "ts",
      -  "actor",
      -  "summary",
      -  "is_bot",
      -  "source",
      -  "hidden",
      -  "deleted",
      -  "proposer"
      -]New value: +[
      +  "ref_id",
      +  "kind",
      +  "ts",
      +  "actor",
      +  "summary",
      +  "is_bot",
      +  "source",
      +  "hidden",
      +  "deleted",
      +  "proposer",
      +  "actor_id",
      +  "proposer_id"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / history / items / properties / is_bot / description
      Previous value: -"Made by an automated process (the Wikidata sync, an import)."New value: +"Made by an automated process: the Wikidata sync, an import, or an account an administrator has marked as automation (a script or agent). A legacy (archive) revision keeps the old wiki’s own flag."
  3. 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 (readOnlyHint true, openWorldHint false), so the description's job is to add context beyond that. It does add ordering ('newest first'), a pagination cue ('next_offset' pages on), and non-obvious behavior for merged entries whose key redirects to its own history, which an agent could not infer from the annotations.

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 compact sentences with the core purpose front-loaded and no filler. The merged-entry caveat is the only secondary detail and it earns its place by preventing a look-up mistake.

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 three-parameter read tool with an output schema (so return shape needn't be explained) and annotations covering safety, the definition is close to sufficient. The remaining shortfall is the undocumented limit/offset semantics, which is minor given the tool's simplicity.

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 only 33%: `entry` is documented, but `limit` and `offset` are bare. The description partially compensates by signalling cursor-style paging via `next_offset`, but it never explains the limit default/max or how offset interacts with paging, leaving a gap.

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 states a specific verb and resource ('An entry's public edit history'), which an agent can distinguish from read-style siblings like get_entry or get_article_history. It stops short of explicitly naming the sibling it differs from, so it is clear but not fully differentiated.

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?

The word 'public' implies a read-only viewing use case, and the merged-entry sentence hints at when the entry key resolves elsewhere. However, there is no explicit when-to-use versus get_entry or get_article_history, and no guidance on which entry identifier form to prefer beyond what the schema already says.

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.