Skip to main content
Glama

below

Lists every stratigraphic unit earlier than a specified unit, returning all units it seals for Harris matrix and excavation sequencing analysis.

Instructions

Every unit stratigraphically earlier than unit (everything it seals).

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

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.7/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 behavioral burden, yet it says nothing about permissions, result ordering, or pagination behavior. A `limit` parameter defaulting to 200 strongly implies paging, but the description never mentions truncation or how to page.

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?

A single tight sentence with the key relation front-loaded and no filler. Its brevity is appropriate for the sentence itself, even if the overall definition is under-specified.

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?

The existence of an output schema means return values need not be described, but the definition leaves the `site` and `limit` parameters undocumented and provides no behavioral or selection context. For a three-parameter query with zero schema coverage, this is insufficient.

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%, and the description only glosses the required `unit` parameter. The optional `site` scope and the `limit` control are left entirely unexplained, so an agent gets no meaning for two of three parameters.

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?

States a specific resource (units) and a specific relation (stratigraphically earlier than the given unit, i.e. everything it seals). The parenthetical adds a second framing that makes the intent unambiguous, though it does not explicitly name a sibling such as 'above' to sharpen the contrast.

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 use this versus the complementary 'above' tool or the generic 'relation'/'query' tools. The only usage signal is the implied stratigraphy context, which an agent must infer from the wording.

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