Skip to main content
Glama

relation

Determine whether two stratigraphic units are earlier, later, same, contested, or unknown, and retrieve the record chain and contested direct claims that prove the ordering.

Instructions

How two units relate: earlier, later, same, contested or unknown, with the chain of records that proves it and any contested direct claims.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "relation"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes
bYes
siteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry behavioral disclosure. It does explain that results include a chain of records proving the relation and any contested direct claims, which adds meaningful context, but it does not say whether the operation is read-only, what permissions are needed, whether it has side effects, or how errors and ambiguity are handled.

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 a single compact, front-loaded sentence with no obvious filler. Its structure is efficient, though the term 'units' is left undefined and the colon-led enumeration is slightly fragmentary.

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 the description need not explain return values in detail. However, for a tool with three undocumented parameters and no annotations, it leaves critical gaps: what a, b, and site mean, and when this lookup should be used instead of related tools.

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 three parameters. The description only implies that a and b are the two units being compared; it says nothing about the site parameter or input formats, so it barely compensates for the undocumented schema.

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 clear query purpose: determining how two units relate, with enumerated outcome classes (earlier, later, same, contested, unknown) and supporting evidence. It is more specific than the tool name alone, but it does not explicitly distinguish this from siblings such as propose_relation, above, below, or resolve_order.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The purpose implies it is for looking up an existing relation between two units, but the description does not tell the agent when that is preferable to sibling tools.

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