kb-newspapers-mcp

Overview Schema Source Related Servers Discussions Admin

search_in_issue

Find every occurrence of a word or phrase inside a specific newspaper issue, returning exact text lines and coordinates for highlighting. Use to retrieve complete sentences when a search snippet is cut off.

Instructions

Search inside a specific newspaper issue to locate all occurrences of a word or phrase
with exact text lines and coordinates for image highlighting (IIIF Content Search).

Two-Stage Workflow Usage:
Use this tool as Stage 2 after 'search_newspapers' whenever a snippet is cut off or you need
the complete surrounding sentence (e.g. to uncover full names, occupations, causes of death,
travel origins/destinations, or accompanying persons).

Args:
    package_id: The package ID of the newspaper issue (e.g. 'dark-37858').
    query: Search word or phrase to locate within the issue.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`package_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 16, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It explains the purpose and hints at the output (text lines and coordinates), but does not disclose potential limitations like result limits, OCR inaccuracies, or performance constraints. It adds context beyond the schema but leaves some gaps about operational behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: it starts with the primary purpose, then gives a workflow usage section, and finally the Args. It is concise with minimal fluff, though the workflow section could be slightly more compact, but overall it is easy to digest.

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?

The tool has an output schema (the prompt mentions 'Has output schema: true'), so return values are handled. The description covers the primary use case, workflow integration, and parameter examples. It does not mention edge cases like empty results or multi-page handling, but for a search tool with clear schema and workflow, it is sufficiently complete.

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 0%, so the description must clarify parameter meaning. It explains 'package_id' with an example ('dark-37858') and clarifies that 'query' is the search term. This adds value, but since both parameters are self-evident from names and are well-described, the description does not need to over-explain.

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 states the specific action ('Search inside a specific newspaper issue'), the resource (issue), and the output (all occurrences with exact text lines and coordinates for highlighting). It also explicitly names the sibling 'search_newspapers' and differentiates itself as a stage 2 follow-up, making it clear what this tool does that others don't.

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 gives explicit when-to-use guidance ('Use this tool as Stage 2 after 'search_newspapers' whenever a snippet is cut off or you need the complete surrounding sentence') and provides concrete example use cases (uncovering full names, occupations, etc.), which helps the agent decide when to invoke this tool versus alternatives.

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

Deploy Server