Skip to main content
Glama

Metis — Audit Background Provenance

audit_background_provenance

Records DOIs for indexed documents across knowledge layers by matching local references first and optionally querying Crossref, so each layer can verify its own provenance.

Instructions

Where did the documents in the knowledge layers actually come from?

Sweeps `pdf_index_state` and records a DOI for every indexed document it can
identify, so a layer can state its own provenance. Matches against the local
reference library first — that is free and covers most of the corpus — and
only calls Crossref when `resolve_online` is set.

This is the "verify at ingest, trust at read" half of the verification layer.
A corpus of known-real documents makes answer-time checking a containment
problem rather than a truth problem, and the cost is paid once per document
instead of once per claim.

Args:
    layer: Restrict to one layer slug (e.g. 'epi-methods'); omit for all.
    resolve_online: Also query Crossref by title for documents the local
        library cannot identify. Metadata only; costs one request each.
    limit: Maximum documents to process in one pass (default 400).

Returns:
    Per-layer provenance counts and what changed in this pass.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
layerNo
limitNo
resolve_onlineNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose the important traits: the tool writes DOI state, prefers a free local match, and incurs one external request per unresolved document. It stops short of stating idempotency, failure behavior, or whether recorded DOIs are overwritten.

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?

The operational content is front-loaded and useful, but the 'verify at ingest, trust at read' paragraph is rationale rather than invocation guidance and does not help an agent decide or call correctly. Roughly a third of the text is philosophical framing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so the brief 'Returns' note suffices. For a mutating audit pass with three params, the cost model, scope control, and side effect are all covered; only error/retry behavior and overwrite semantics are missing.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does: `layer` is a slug with an example and an omit-for-all rule, `resolve_online` explains the Crossref trigger and cost, and `limit` is the per-pass cap. It adds real meaning beyond the bare defaults in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource: it sweeps `pdf_index_state` and records a DOI for every indexed document. The opening question plus the explicit mention of the local library and Crossref makes it clearly distinct from siblings like `mine_references` or `index_pending_layers`.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear selection logic for the key branch — local library first, Crossref only when `resolve_online` is set, with the cost trade-off spelled out. It does not name an explicit alternative sibling tool to use instead, which keeps it below a 5.

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