Skip to main content
Glama

Search USVI public records

search
Read-onlyIdempotent

Find U.S. Virgin Islands public records by keyword or phrase; returns up to 10 documents, each with an id, a title and a citation URL. Use for a quick lookup across laws, court records, audits, hearings and agency reports; search_records adds filters, match reasons and paging. Searches the full extracted text of the archive's documents, plus their catalogue records. Not covered: the archive's newspapers (the St. Croix Avis, The West End News, Home Journal and the St. Croix Tribune) and the Danish West Indies papers it opens for search, which are on its separate newspaper connector (the 2026 Virgin Islands Code is here, in search_code and get_code_section); and anything the archive has not published. Withheld and withdrawn documents are absent, not hidden.

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 search 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.6/5.0
Behavior4/5

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

Annotations already carry readOnly, idempotent, non-destructive and closed-world hints, yet the description adds real context: a hard cap of 10 results, the returned fields (id, title, citation URL), what corpus is searched, and that withheld/withdrawn documents are absent rather than hidden. Only slightly short of ideal because ranking or relevance behavior is unstated.

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 core action and result shape, then layers alternatives and exclusions in descending importance. The newspaper-name parenthetical and the nested aside about the Virgin Islands Code are dense and slightly verbose, but each sentence contributes scope information.

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, read-only search tool with no output schema, the description supplies result count, result fields, corpus coverage and absence semantics. An agent has everything needed to select and invoke it correctly.

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% for the single query parameter, so baseline is 3-4. The description reinforces that both keywords and intact phrases are accepted, matching the schema's quoting hint without adding new syntax beyond it.

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 U.S. Virgin Islands public records by keyword or phrase"), plus scope of coverage (full extracted text plus catalogue records). It explicitly distinguishes itself from siblings search_records (adds filters/paging), search_code/get_code_section (the Code), and a separate newspaper connector.

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 when-to-use guidance ("Use for a quick lookup across laws, court records, audits, hearings and agency reports") and names the alternative that adds filters, match reasons and paging. It also enumerates exclusions — newspapers, Danish West Indies papers, unpublished material — so an agent knows when not to use it.

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