Skip to main content
Glama

above

Lists all stratigraphic units that occur later than a given unit, helping archaeologists query Harris matrix ordering and identify overlying deposits.

Instructions

Every unit stratigraphically later than unit.

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

Input Schema

NameRequiredDescriptionDefault
siteNo
unitYes
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.2/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing: not that the call is a read-only lookup, not that results are bounded (the `limit` default of 200 strongly implies truncation but that is never stated), and not whether an unknown `unit` errors or returns empty. A single relational phrase is inadequate for a tool with zero annotation coverage.

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?

It is a single short sentence with no padding, which is good, but it is a sentence fragment rather than a front-loaded statement of action plus result. Brevity here reflects under-specification, not disciplined editing.

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 shape need not be described. However, for a query tool with a 200-item default limit the description should still signal truncation behavior and the meaning of `site`, and it says nothing about either. The one sentence present is accurate but leaves too much to inference.

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% across three parameters, so the description must compensate and it covers only `unit`, defining it as the stratigraphic anchor. The `site` parameter (what a site scopes — locality, project, dataset?) and `limit` (page size, silently defaulting to 200) receive no explanation anywhere in either the schema or the description.

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 description gives the domain meaning of the tool: it returns every unit stratigraphically later than the named `unit`. That is more informative than the bare name 'above', but it is a noun phrase with no verb (list/return/fetch), so an agent must infer this is a retrieval tool rather than a relation-creation or ordering tool, and no explicit contrast with the sibling `below` is drawn.

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 guidance on when to call this versus `below`, `relation`, `resolve_order`, or `date_bracket`, all of which plausibly touch stratigraphic ordering. The only implicit signal is the word 'stratigraphically', which does not tell the agent what question this tool answers or when it should be preferred.

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