Skip to main content
Glama

Evaluate Reconstruction Coverage

evaluate_reconstruction_coverage
Read-onlyIdempotent

Evaluate reconstruction coverage against a named boundary; classify missing ownership/inventory as partial, stale/weak/unresolved proof as unknown, and fail closed on contradictions or failed proof.

Instructions

Evaluate inline evidence-backed reconstruction coverage against one named boundary. Missing ownership or inventory is partial; stale, weak, truncated, skipped, or unresolved proof is unknown; contradictions, failed proof, missing owners, and authority routing fail closed.

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": {
      "coverage": {
        "claims": [],
        "owners": [],
        "surfaces": [],
        "artifacts": [],
        "boundaries": [
          {
            "title": "CLI replacement",
            "boundary_id": "replacement.cli",
            "required_claim_ids": [
              "claim.cli.help"
            ],
            "allowed_unknown_ids": [],
            "allowed_dispositions": [],
            "required_surface_ids": [
              "cli.help"
            ],
            "required_package_proof_kinds": [
              "clean-install",
              "authority-independence"
            ]
          }
        ],
        "contradictions": [],
        "package_proofs": [],
        "evidence_bundle": {
          "records": [],
          "captures": [],
          "unknowns": [],
          "artifacts": [],
          "providers": [],
          "scenarios": [],
          "environments": []
        },
        "verifier_results": [],
        "verifier_contracts": [],
        "residual_unknown_ids": []
      },
      "boundary_id": "replacement.cli"
    },
    "name": "evaluate_reconstruction_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
coverageYesExact reconstruction-coverage commitment to verify.
boundary_idYesExact reconstruction boundary identifier to evaluate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish this as a safe, idempotent, closed-world read. The description goes meaningfully beyond them by declaring the verdict taxonomy: missing ownership or inventory yields partial, stale/weak/truncated/skipped/unresolved proof yields unknown, and contradictions, failed proof, missing owners, or authority routing fail closed. That is real behavioral disclosure an agent cannot get from the annotations or 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?

Two sentences, front-loaded with the purpose, then the classification rules. Every clause carries distinct semantic weight with no filler, despite heavy domain jargon.

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 tool taking a large structured coverage commitment with no output schema, the description explains how verdicts are assigned but not what the response actually contains (per-boundary status? per-claim findings?). The classification rules compensate partly, but an agent still cannot anticipate the return shape.

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% with only two parameters, so the schema already documents coverage and boundary_id. The phrase 'one named boundary' reinforces that boundary_id selects a single boundary rather than a set, adding marginal meaning over the schema, but nothing about expected structure or identifier format is added.

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 specific verb and object: evaluate evidence-backed reconstruction coverage against one named boundary. That is concrete and distinguishable from ledger-building or verification siblings, but it does not name any sibling explicitly, so differentiation is left implicit.

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?

Usage is implied by 'against one named boundary,' but there is no explicit when-to-use statement, no exclusion, and no mention of the sibling tools (build_reconstruction_obligation_ledger, verify_reconstruction) that an agent must choose between. The agent can infer context but not the selection rule.

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