Skip to main content
Glama

What the corpus is

research_corpus
Read-onlyIdempotent

Size, span (1736-1963), decade histogram, quality and caution shares, and coverage of Chronicling America (English-language titles are the target). Call once before searching so a negative result means something. Free.

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": "research_corpus"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
docsYesEvent docs in the index
issuesYesIssues with at least one component in the corpus
statesYes
titlesYesNewspaper titles (LoC lccns) with processed issues
decadesYesdocs per decade, e.g. {"1850": 24387}
year_maxYes
year_minYes
componentsYesComponents (a multi-event notice is one component, N docs)
last_ingestYes
caution_docsYesdocs flagged offensive by modern standards
quality_tiersYesdocs per tier (green / yellow / red). red is reported here and withheld everywhere else: never a hit, a facet bucket or a fetchable component. Every other count is the served corpus.
embed_worthy_docsYesdocs with a vector (semantic search can see them)
denominators_computed_atNoCounted live, cached ~1 h
issues_in_chronicling_americaNoEvery issue LoC has published for an ENGLISH-LANGUAGE title — the target corpus and the coverage denominator; refreshed with the crawler
coverage_of_chronicling_americaNoissues / issues_in_chronicling_america
issues_in_chronicling_america_all_languagesNoSame across all languages, for reference (English is > 95 %)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: it is free to call, should be called once, and the corpus is scoped to English-language titles of Chronicling America, which warns the agent about coverage limits.

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?

Dense and front-loaded: contents first, then the operational instruction, then the cost note. The telegraphic phrasing ('quality and caution shares') is compact but slightly opaque on first read.

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?

With an output schema present and zero parameters, the description does not need to enumerate return fields, yet it still sketches them. Cost, one-call guidance, and the English-language coverage caveat cover what an agent needs before invoking it.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline is high. The description's clauses about span and coverage describe the return payload rather than any input semantics.

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

Purpose4/5

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

The description names the concrete payload: size, time span (1736-1963), decade histogram, quality/caution shares, and Chronicling America coverage. An agent knows exactly what it gets back, though the verb is implicit ('what the corpus is' rather than 'return corpus statistics').

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?

Explicit timing guidance: 'Call once before searching so a negative result means something,' which tells the agent both when to invoke it and that a single call suffices. It stops short of naming a specific alternative sibling to consult instead for other needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources