Skip to main content
Glama

period_sequence

Returns the period-to-period sequence for an archaeological site by counting stratigraphic matrix order, showing which period lies directly above which.

Instructions

Which period lies directly over which, counted over the matrix: the site's sequence.

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": {
      "site": "<site>"
    },
    "name": "period_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2/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 behavioral burden. It does not state whether the operation is read-only, whether it computes or merely returns an existing sequence, what permissions are needed, or what 'matrix' means operationally, leaving the agent with almost no behavioral context.

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

Conciseness2/5

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

The definition is short but not front-loaded with a clear action, and the single sentence is cryptic rather than efficient. Brevity here reflects under-specification rather than disciplined conciseness.

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?

Although an output schema exists, the description does not explain the tool's behavior, the meaning of the period relationship, or the input's semantics. For a tool with a required parameter and no annotations, this leaves major gaps an agent needs filled before 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% for the single required 'site' parameter. The description refers to 'the site's sequence' but never explains whether 'site' is an identifier, name, or domain, nor how it affects the returned period ordering.

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

Purpose2/5

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

The description names a resource (the site's period sequence) but has no clear verb and leans on unexplained jargon like 'matrix' and 'counted over the matrix'. It does not distinguish this from siblings such as above, below, resolve_order, or relation, so an agent cannot confidently tell what this tool actually does.

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 explicit when-to-use guidance, no exclusions, and no named alternatives. The phrase 'the site's sequence' implies a retrieval or ordering operation but gives no condition under which this tool should be chosen over related ordering tools like resolve_order or relation.

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