Skip to main content
Glama

corpus_provenance

Explains the dataset's source, curation, and known limits to clarify whose words are included and when coverage is missing.

Instructions

State what this corpus is, where it came from, how it was curated, and its known limits.

Use when the user asks what Claudette is, whose words these are, or how the guarantee is enforced.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
statusYesok — passages found that match most of the question's terms. weak — something matched, but thinly; say so if you use it. no_coverage — the corpus does not speak to this. Say that. Do not answer from elsewhere. not_found — a specific reference did not resolve.
constraintNoAnswer only from these passages. Quote or closely paraphrase, and cite each claim as [Author, Title §n]. If the passages do not speak to the question, say so plainly rather than filling the gap from elsewhere.
provenanceNoEvery passage is from a work by a named woman author. Each hit's `source` says where that text came from and on what basis; `curated` says whether a person reviewed the edition.
limitationsNoPart of the answer, not a disclaimer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.2
    • changedOutput schema / properties / provenance / default
      Previous value: -"Every passage is from a work by a named woman author, in the public domain, via Project Gutenberg."New value: +"Every passage is from a work by a named woman author. Each hit's `source` says where that text came from and on what basis; `curated` says whether a person reviewed the edition."
  2. First observedv0.1.0

TDQS

A4.7/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 burden. It clearly indicates an informational read ("State what...") implying no side effects, but it does not explicitly mention read-only or safety traits. However, for a simple provenance query, this level of transparency is adequate and there is no contradiction.

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 two sentences with no wasted words. The core purpose is front-loaded, followed by precise usage guidance. Every word earns its place, achieving maximal efficiency.

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?

With an output schema present and no parameters, the description covers all necessary information for correct invocation. It states what the tool does and when to use it, leaving no gaps for an agent to call it incorrectly.

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?

The input schema has zero parameters, so baseline is 4 per rubric. The description does not need to elaborate on parameters since there are none, and it appropriately focuses on the tool's purpose and usage.

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 clearly states the tool's purpose: 'State what this corpus is, where it came from, how it was curated, and its known limits.' This is a specific verb-resource pair, and it is distinct from sibling tools like search_corpus or read_passage, which focus on querying or reading content rather than provenance.

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?

The description explicitly provides usage scenarios: 'Use when the user asks what Claudette is, whose words these are, or how the guarantee is enforced.' This directly guides the agent on when to invoke this tool versus siblings, offering concrete triggers and implicitly contrasting with other tools.

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