Skip to main content
Glama

recheck

Recomputes matrix depth, contested claims, and outstanding issues for an archaeological site to keep stratigraphic analysis and records consistent.

Instructions

Recompute matrix depth, contested claims and issues for a site.

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

Input Schema

NameRequiredDescriptionDefault
siteYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does not say whether recomputation persists state, is idempotent, is expensive/long-running, requires elevated permissions, or invalidates cached results. Only the return shape is covered elsewhere, via the existing output schema.

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

Conciseness5/5

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

One front-loaded sentence naming the operation and its effects, with no filler or redundant restatement of the name. Nothing is wasted.

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 output schema relieves the description of explaining return values, but for a recomputation operation with zero annotation coverage the definition still omits idempotency, cost, permissions, and the site identifier format. As written, an agent cannot confidently predict side effects before invoking it.

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?

The single required "site" parameter has 0% schema description coverage, and the description only implies site scoping without stating the identifier format (ID, slug, or name) or whether it accepts aliases. At low coverage the description should compensate, and it does not.

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 uses a specific verb ("Recompute") and names three concrete outputs (matrix depth, contested claims, issues) scoped to a site, so an agent can tell this is a derived-state recomputation rather than a plain query or mutation. The term "matrix depth" is domain jargon left unexplained, and it does not explicitly differentiate itself from siblings like issues or history.

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 siblings such as issues, history, or revert, no prerequisites or preconditions, and no statement of when not to use it. The agent must infer that recomputation is appropriate after upstream data changes.

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