Skip to main content
Glama

Search the Virgin Islands Code

search_code
Read-onlyIdempotent

Search the 2026 Virgin Islands Code section by section, by words or by citation (e.g. "1 V.I.C. § 254"). Use for questions about what the Code says. Returns up to 10 sections, each with its citation, title, heading, a short excerpt and its page on usvipublicrecords.com; get_code_section gives a section's full text. The words together as written rank first, then every word, then some. The text is an unofficial word-for-word copy of the 2026 edition as found, for reference, not for legal reliance, and every answer says so; acts passed after the edition are not reflected.

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_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10, maximum 25.
queryYesWords, or a citation such as "33 V.I.C. § 3021" or "title 3 section 551".
titleNoOnly this title of the Code: "1" to "34", or "11A", "12A", "15A".
offsetNoResults to skip, for paging.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, and the description adds substantial behavior beyond them: result cap (up to 10), the fields returned per hit, the ranking order (exact phrase, then all words, then some), and two important caveats — unofficial copy, not for legal reliance, and acts passed after the 2026 edition are not reflected.

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 and routing, then returns, then ranking, then caveats — a sensible order with no filler. The ranking sentence ('The words together as written rank first, then every word, then some') is slightly compressed and could be clearer, but nothing is wasted.

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?

There is no output schema, and the description compensates by enumerating the returned fields (citation, title, heading, excerpt, page URL) and the result cap. Combined with the ranking and disclaimer notes, an agent has everything needed to call this correctly and to frame the results honestly.

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 100%, so the schema already documents query, title, limit and offset including defaults and bounds. The description only repeats the citation-format idea already present in the query description and restates the default result count, adding little new meaning about parameter behavior.

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 with scope: 'Search the 2026 Virgin Islands Code section by section, by words or by citation.' It also names the sibling it complements ('get_code_section gives a section's full text'), so an agent can distinguish a search operation from a full-text retrieval without opening either 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?

'Use for questions about what the Code says' gives a positive selection condition, and the pointer to get_code_section defines the alternative for retrieving a full section. The routing decision is explicit rather than inferred.

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