Skip to main content
Glama

date_bracket

Calculates an archaeological unit’s terminus post quem and ante quem from dated units below and above it and verifies whether its recorded date fits.

Instructions

Terminus post quem and ante quem for a unit from the dated units below and above it, and whether its recorded date fits. Years are astronomical: -1899 is 1900 BCE.

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": {
      "unit": "<unit>"
    },
    "name": "date_bracket"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNo
unitYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose genuinely useful context: the bracket is derived from neighboring dated units and years are astronomical (-1899 = 1900 BCE). It does not say what happens when the unit or its neighbors are undated, whether the tool errors or returns an open bracket, or whether it is a pure computation versus a stored mutation.

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 tight sentences, front-loaded with the core computation and followed by the one unit convention an agent could easily get wrong. Nothing is wasted and nothing important is buried.

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 computation and year convention are covered. However, for a tool whose behavior depends on neighboring units, the missing edge-case behavior and the undocumented site/unit parameters leave real gaps.

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 the two parameters. It says nothing about what a unit identifier is or what the optional site scoping means or how a null/default site is interpreted; 'unit' is only obliquely referenced via 'below it and above it'. The astronomical-year note helps interpret returned dates, not the inputs.

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 operation on a specific resource: it derives terminus post quem and ante quem for a unit from the dated units below and above it, and checks whether the recorded date falls inside that bracket. That is clearly distinct from catalog-style siblings like history or provenance, though it never names a sibling to route against.

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?

Usage is implied by the verb and inputs — call this when you want a date bracket for a given unit — but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as above/below or query for related lookups. The agent must infer the trigger condition.

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