Skip to main content
Glama

Verify Unknown Resolution

verify_unknown_resolution
Read-onlyIdempotent

Revalidates a residual-unknown resolution against live evidence, exact authority/confidence/environment requirements, and revision integrity so only current, supported truth claims pass.

Instructions

Revalidate the current residual-unknown head against live bundled evidence, exact authority/confidence/environment requirements, and revision integrity. Withdrawn and out-of-scope dispositions are not truth claims.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "unknown_id": "unk_0000000000000000000000000000000000000000000000000000000000000000"
    },
    "name": "verify_unknown_resolution"
  }
}

Input Schema

NameRequiredDescriptionDefault
unknown_idYesExact residual-unknown identifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real context beyond that: revalidation happens against live bundled evidence and revision integrity, and it warns that withdrawn/out-of-scope dispositions do not constitute truth claims. It still does not say what a failed or indeterminate revalidation looks like, which is the main behavioral gap.

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

Conciseness3/5

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

Two sentences with no filler, and the verification target is front-loaded. However, the middle clause ('exact authority/confidence/environment requirements') is compressed jargon that costs more comprehension than it saves in length.

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?

For a single-parameter read-only check this covers the target and the criteria reasonably well. With no output schema, though, the description should indicate what a verification result looks like (pass/fail, which criteria were unmet), and it does not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the single unknown_id parameter is documented in-schema with an exact pattern, so the baseline of 3 applies. The description adds no meaning about the identifier beyond calling it the 'current residual-unknown head'.

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 specific verb ('Revalidate') and a specific object ('the current residual-unknown head'), plus the evidence it is checked against (live bundled evidence, authority/confidence/environment requirements, revision integrity). That is far more concrete than a restated title, though the heavy domain jargon ('residual-unknown head') and absence of any sibling contrast keep it from a 5.

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 statement of when to call this versus record_unknown, update_unknown, verify_reconstruction, or the other verify_* tools, and no prerequisites or trigger conditions. The second sentence constrains interpretation of outcomes ('withdrawn and out-of-scope dispositions are not truth claims') rather than telling the agent when this tool is the right choice.

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

Deploy Server

Other Tools