Skip to main content
Glama

resolve_order

Resolve disputed stratigraphic unit ordering by recording which unit is later and rejecting contrary claims while preserving them for review; confirm with the user before committing.

Instructions

Settle a disputed pair: upper is the later unit. Contrary claims become :REJECTED (kept, not deleted). Confirm with the user first.

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": {
      "upper": "<upper>",
      "lower": "<lower>",
      "note": "<note>"
    },
    "name": "resolve_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
siteNo
lowerYes
upperYes
authorNoagent

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses that contrary claims are moved to :REJECTED and explicitly kept rather than deleted, which is a crucial non-destructive guarantee. It also flags the human-confirmation requirement. It doesn't address reversibility or idempotency, keeping it just short of the top score.

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?

Three short clauses, each earning its place: the core action, the rejection consequence, and the confirmation requirement. The action is front-loaded and there is no filler, though the opening phrase is slightly abstract.

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 needn't be explained, and the rejection/confirmation behavior is well covered. The large gap is parameter meaning: four of five parameters are undocumented in both schema and description, which is a notable omission for a five-parameter mutation tool.

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 five parameters, so the description must compensate. It only clarifies `upper` (the later unit) and leaves `lower`, `note`, `site`, and `author` entirely undefined, meaning most parameters remain ambiguous to the caller.

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 gives a concrete verb ("Settle") and resource ("a disputed pair") and clarifies the decisive semantic that `upper` is the later unit. The domain term "unit" and the nature of the pair are not fully defined, but the core action is unambiguous enough to act on.

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?

It states a clear interaction prerequisite ("Confirm with the user first") and implies the situation where it applies (a disputed pair). However, it never names an alternative such as propose_relation or revert, so the agent gets no explicit guidance on when to choose this over related sibling tools.

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