Skip to main content
Glama

Compare retained snapshots

get_snapshot_changes
Read-onlyIdempotent

Page added/updated/deleted records between retained snapshots from this Omeka instance. Lists available snapshot IDs when fewer than two exist. For recent additions without history, use added_since on the search tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 30, max 100
to_idNo
corpusNo
offsetNo
from_idNo

Output Schema

NameRequiredDescriptionDefault
hintNo
countNo
to_idNo
offsetNo
reasonNo
statusYes
from_idNo
resultsNo
has_moreNo
snapshotsYes
next_offsetNo
total_matchesNo
effective_limitNo
requested_limitNo
response_limitedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / corpus / enum
      Previous value: -[
      -  "persons",
      -  "organisations",
      -  "locations",
      -  "projects",
      -  "research_sections",
      -  "research_items",
      -  "publications",
      -  "journals",
      -  "podcasts",
      -  "videos",
      -  "playlists",
      -  "languages",
      -  "item_sets",
      -  "subjects"
      -]New value: +[
      +  "persons",
      +  "organisations",
      +  "locations",
      +  "projects",
      +  "research_sections",
      +  "research_items",
      +  "publications",
      +  "journals",
      +  "podcasts",
      +  "videos",
      +  "playlists",
      +  "languages",
      +  "item_sets",
      +  "subjects",
      +  "chronicles"
      +]
    • addedOutput schema / properties / hint
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / reason
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / results / items / required
      Previous value: -[
      -  "corpus",
      -  "id",
      -  "change",
      -  "title",
      -  "amira_url"
      -]New value: +[
      +  "corpus",
      +  "id",
      +  "change",
      +  "title"
      +]
  2. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / results / items / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / snapshots / items / additionalProperties
      Removed value: -false
  3. Changed1 schema field changed
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
  4. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavior beyond that: results are paginated, and when fewer than two snapshots exist the call degrades into listing available snapshot IDs rather than erroring — a useful surprise to disclose.

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?

Three tight sentences with no filler: purpose first, then the empty-state behavior, then the alternative routing. Each sentence carries distinct information an agent needs.

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?

An output schema exists, so return values need not be described, and the fallback/alternative behavior is covered. However, for a 5-parameter tool with no required parameters and near-empty schema descriptions, the undefined defaults for from_id/to_id and the unexplained corpus enum leave the agent guessing at invocation details.

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

Parameters2/5

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

Schema coverage is only 20%, so the description must carry the load, and it largely does not. 'Between retained snapshots' hints at from_id/to_id but never names them or says what happens when they are omitted (e.g., defaulting to the latest two), and the 15-value corpus filter and offset/limit paging are not explained at all.

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 uses a specific verb ('Page') against a specific resource ('added/updated/deleted records'), scoped precisely to 'between retained snapshots from this Omeka instance'. That scope distinguishes it from generic retrieval siblings, though it never explicitly names compare_collections as a related diff tool.

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 routes one concrete case away from this tool: 'For recent additions without history, use added_since on the search tools.' It also implicitly frames the primary case (comparing two retained snapshots) but offers no exclusion for when to prefer compare_collections or other diff-style siblings.

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.