Skip to main content
Glama

Get provenance chain

mcai_provenance
Read-onlyIdempotent

Trace a term definition back to its sources: get definition type, document sections, character ranges, editions, evidence quotations, and relation evidence for verification or edition comparison.

Instructions

Return the full provenance chain for a term: definition type, source documents with section, location, character range and edition, supporting evidence quotations, and relation evidence. Use when the caller must verify where a definition comes from, or compare editions. Routing: citations only -> mcai_cite; full entry -> mcai_concept. Boundary: returns recorded provenance only; fields absent in the knowledge base are omitted, not inferred.

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": {
      "term": "<term>"
    },
    "name": "mcai_provenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesExact term name, alias, or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.8

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish that this is a safe, idempotent read operation. The description adds meaningful behavior beyond them by listing the provenance fields returned and stating that absent knowledge-base fields are omitted rather than inferred, which prevents over-interpretation. It does not describe response formatting or pagination, but that gap is minor for this retrieval tool.

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?

The description is a single compact paragraph that front-loads the return contents, then gives usage, routing, and boundary information. Every sentence adds routing or behavioral value without repetition.

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

Completeness5/5

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

This is a simple one-parameter read tool with annotations and no output schema. The description supplies return contents, use cases, sibling routing, and omission semantics, which is enough for correct invocation and interpretation.

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 coverage is 100%, and the term parameter is documented as an exact term name, alias, or slug. The description only says the chain is for a term and adds no further resolution or ambiguity guidance beyond the schema. A baseline 3 is appropriate because the schema carries parameter semantics.

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?

The description uses a specific verb and resource: return the full provenance chain for a term. It enumerates the chain components and explicitly distinguishes this tool from sibling tools for citations and full concept entries.

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

Usage Guidelines5/5

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

It states concrete use cases, verifying where a definition comes from or comparing editions, and provides explicit routing: citations only go to mcai_cite, full entry goes to mcai_concept. The boundary clause further clarifies that only recorded provenance is returned.

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