Skip to main content
Glama

USVI Public Records: Newspapers

Search the Virgin Islands newspapers

search
Read-onlyIdempotent

Find pages of U.S. Virgin Islands newspapers by keyword or phrase; returns up to 10 pages, each with an id, a citation title and a URL. Use for a quick lookup in the islands' press. Better matches come first (the phrase as written, then every word, then some); among equal matches every paper gets its best page in before any paper gets a second, so one long-running paper cannot hide the others. search_newspapers adds paper and date filters, match reasons and 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. 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for. Plain language is fine; quote a phrase to require it intact.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), and the description adds behavior they cannot: a 10-page result cap, the ranking order (phrase, then every word, then some), the fairness rule that each paper gets its best page before any paper gets a second, and the OCR-error caveat with a link to the holding library's copy. It also warns that hit counts are pages, never articles.

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-loaded with purpose, results and ranking before caveats, and every sentence carries information an agent needs. It runs long, with the full paper inventory and date spans occupying several lines, but nothing is filler.

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 one-parameter, no-output-schema tool this is thorough: it describes the return fields (id, citation title, URL), the result cap, ranking, corpus gaps, OCR reliability and the interpretive limit ('a lead to the primary record, not evidence on its own'). An agent has enough to invoke and to present results responsibly.

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% and the schema already explains that plain language works and quoting requires a phrase intact. The description still adds value by spelling out the matching consequences (phrase as written, then every word, then some), which tells the agent why quoting matters in practice.

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 ('Find pages of U.S. Virgin Islands newspapers by keyword or phrase') plus the scope of the corpus (four named papers with date ranges). It distinguishes itself from search_newspapers, search_danish_papers and the separate document connector by name, so an agent can route without opening any schema.

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 frames this as the quick-lookup tool and routes richer needs to search_newspapers ('adds paper and date filters, match reasons and paging'). It also excludes two adjacent domains by name: laws/audits/court records on the document connector, and Danish West Indies papers on search_danish_papers.

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