claudette

read_passage

Retrieve a passage verbatim from a citation ref, including neighboring passages, to verify quotes and check sources after searching the corpus.

Instructions

Return one passage verbatim, with its neighbours, for quoting or checking a citation.

Use after search_corpus when you need the surrounding text. Not for finding
passages — it takes a ref, not a question.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ref`	Yes	A citation ref from search_corpus, e.g. 'follett-new-state§412'.
`context`	No	How many neighbouring passages to include either side.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`status`	Yes	ok — 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.
`constraint`	No		Answer 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.
`provenance`	No		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.
`limitations`	No	Part of the answer, not a disclaimer.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.5.2Sep 19, 2026

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."

First observedv0.1.0Sep 18, 2026

TDQS

A4.7/5.0

Behavior4/5

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

No annotations exist, so the description carries the behavioral burden. It clearly frames the tool as a read-only retrieval ('Return one passage verbatim') and adds non-obvious workflow behavior ('after search_corpus', 'takes a ref, not a question'). It does not detail error handling or auth, but the read-only nature is unambiguous.

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 tight sentences with no fluff. The main action and result are front-loaded, and the usage guidance and exclusion are stated in a compact second sentence.

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?

For a simple two-parameter read tool with a fully described schema and an output schema present, the description provides everything needed: what it returns, when to use it, how it relates to siblings, and what it is not for.

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 coverage is 100%, so the baseline is 3. The description adds value by clarifying that ref is a citation reference and not a search query ('takes a ref, not a question'), and 'with its neighbours' reinforces the context parameter's purpose.

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 specific action and resource: 'Return one passage verbatim, with its neighbours'. It also differentiates itself from search_corpus by clarifying it is for quoting/citation checking and 'takes a ref, not a question'.

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?

Explicitly tells the agent when to use it: 'Use after search_corpus when you need the surrounding text.' It also gives an exclusion: 'Not for finding passages', pointing to the alternative search_corpus.

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

Deploy Server