Skip to main content
Glama

history

Retrieve interpretive edits made to an archaeological record, newest first, so you can review changes and identify contradictions in stratigraphic data.

Instructions

The interpretive edits made to the record, newest first.

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": "history"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses only the ordering ('newest first') and the content type ('interpretive edits'), but says nothing about read-only safety, permissions, pagination behavior, or what happens when no record is specified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single sentence with no wasted words and is front-loaded with the content and ordering. However, it is too terse for the tool's complexity and reads as a fragment rather than a complete operational description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 explained. But with two input parameters at 0% schema coverage and no annotations, the description should explain the parameters and the read-only nature; it does neither, leaving key invocation details absent.

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

Parameters1/5

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

Schema description coverage is 0% for two parameters, and the description never mentions 'site' or 'limit'. It adds no meaning about what these parameters control or how they affect the result.

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

Purpose3/5

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

The phrase 'interpretive edits made to the record, newest first' identifies the resource and ordering, but it lacks a specific action verb like 'list' or 'retrieve' and leaves 'the record' ambiguous. It is clearer than a tautology but does not clearly differentiate itself from siblings such as provenance or query.

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?

The description provides no when-to-use guidance, no exclusions, and no explicit alternative among the many sibling tools. An agent must infer that this is the history-retrieval tool without any routing cues.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.