Skip to main content
Glama

provenance

Trace a find's provenance: its bag, stratigraphic unit, period and site, plus sealing units, open caveats and date bracket. Use it to verify context and dating before interpreting results.

Instructions

Where a find came from and what dates it: find -> bag -> unit -> period -> site, the units sealing it, open caveats, and its date bracket.

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": {
      "find": "<find>"
    },
    "name": "provenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
findYes
siteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it never states that this is a read-only retrieval, what happens when a find is unknown or ambiguous, or what role the optional site plays. It does describe the shape of the returned information (chain, sealing units, caveats, bracket), which is real value. But with zero annotation coverage the absence of any error or scope behavior leaves a significant gap.

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?

The definition is short, front-loaded with the core concept, and wastes no words; the arrow-chain notation efficiently conveys hierarchy. It is slightly cryptic in its second half ('the units sealing it, open caveats, and its date bracket'), where a few more words would have removed ambiguity without bloat.

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 spelled out, and the description does convey the domain model an agent needs to interpret results. However, for a domain-specific stratigraphy tool with 0% parameter documentation and no annotations, the definition leaves the caller unable to reason about the optional site argument or failure modes. Adequate for interpretation, insufficient for correct invocation.

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 description coverage is 0%, so the description must explain both parameters and does not. 'find' is only obliquely implied by the domain vocabulary, and 'site' — an optional, nullable string — is never mentioned at all, leaving its purpose (disambiguation? scope restriction?) entirely unknown. This is precisely the case where the description should compensate for a bare schema and it fails to.

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 resource precisely and enumerates the returned content: the find -> bag -> unit -> period -> site chain, sealing units, open caveats, and a date bracket. That is a concrete, domain-specific picture of what the tool produces, not a restatement of the name. It stops short of 5 because no verb frames the operation and it does not distinguish itself from the sibling 'date_bracket', whose subject matter it explicitly overlaps.

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 statement of when to call this versus alternatives. The sibling set contains directly adjacent tools (date_bracket, above, below, relation, describe), yet the description offers no routing conditions or exclusions. An agent can only infer usage from the fact that a 'find' is required.

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