Skip to main content
Glama

USVI Public Records: Newspapers

Search newspapers with filters

search_newspapers
Read-onlyIdempotent

Search the islands' newspapers with paper and issue-date filters, ranked by how closely each page matches. Use when a question names a paper or a period, or needs paging. Searches the OCR text of the archive's newspapers page by page: St. Croix Avis 1865–2001, St. Croix Tribune 1934–1936, Home Journal 1952–1958, The West End News 1953–1963. Every run has gaps, which list_papers names. Issue dates are reliable here. Each result is ONE PAGE with its paper, date and page number, a TIER (phrase = the words together as written, ranked first; strong = every word on the page, not together; possible = at least half; weak = fewer), the terms it actually matched, and links to the page in the site's reader, the holding library's copy, and its image where the archive holds one. No numeric score. A date range that falls in a gap — whole years, or weeks inside a year — gets a sentence naming the dates the archive does not hold. Results are OCR text, which misreads letters, names and numbers; each links the holding library's copy to check against, and the page image where the archive holds one. A newspaper page is a lead to the primary record, not evidence on its own. Hit counts are pages, never articles. Laws, audits, court records and reports are on the archive's separate document connector. The Danish West Indies papers, 1770–1885 (Royal Danish Library), are a separate collection, searched only by search_danish_papers.

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": {
      "query": "<query>"
    },
    "name": "search_newspapers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10, maximum 50.
paperNoA paper: "St. Croix Avis", "The West End News", "Home Journal", "St. Croix Tribune" (or avis, westendnews, homejournal, tribune).
queryYesPlain language is fine. Quote a phrase to require it intact. OCR misspells names: try variants.
offsetNoResults to skip, for paging. Results are ranked within the best 150 pages.
date_toNoLatest issue date, same forms; a year includes all of it.
date_fromNoEarliest issue date: a year (1928), a month (1928-09) or a day (1928-09-13).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial context beyond the readOnly/idempotent/non-destructive annotations: coverage gaps, the fact that gap-hitting date ranges return a sentence naming missing dates, that results are pages not articles, that there is no numeric score, and that OCR text is unreliable. The tier definitions (phrase/strong/possible/weak) are a real behavioral disclosure. It slightly undersells that `offset` paging is confined to the top 150 ranked pages, though the schema states this.

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?

Front-loads the verb, corpus, and ranking model, then layers filters, output shape, and caveats. It is long but nearly every sentence carries signal; the one clear redundancy is repeating the reader/library-copy/image links twice, once in the result-shape sentence and again in the OCR caveat.

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 no output schema and six parameters, the description carries the full burden and does: it explains result granularity, every result field including the tier taxonomy, the absence of a numeric score, and the OCR reliability caveat with the page-image fallback. It also flags the corpus gaps that affect interpretation of results.

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%, so the schema already documents query quoting, paper aliases, and date forms. The description reinforces date-range behavior through the gap explanation but adds no new meaning for the `paper`, `limit`, or `offset` parameters beyond what the schema provides; its strongest additions concern output shape rather than inputs.

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 verb and resource ("Search the islands' newspapers") plus the filtering and ranking model, and explicitly separates itself from search_danish_papers and the archive's separate document connector. It also enumerates the covered papers with date spans, so an agent knows the exact corpus.

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?

Gives explicit triggering conditions ("Use when a question names a paper or a period, or needs paging") and names exclusions with the right alternative for each: Danish West Indies papers go to search_danish_papers, and laws/audits/court records/reports live on a separate document connector. Nothing is left to inference.

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