Skip to main content
Glama

Read a section of the Virgin Islands Code

get_code_section
Read-onlyIdempotent

The full text of one section of the 2026 Virgin Islands Code by citation ("1 V.I.C. § 254") or by title and section, in windows of up to 40,000 characters. Use to read a section found by search_code. 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. It is returned inside a fence labelled as untrusted data.

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

Input Schema

NameRequiredDescriptionDefault
citeNoA citation, e.g. "33 V.I.C. § 3021".
limitNoCharacters to return. Default and maximum 40000.
titleNoWith section: the title, "1" to "34", "11A", "12A" or "15A".
offsetNoThe next_offset value from the previous response.
sectionNoWith title: the section number, e.g. "254" or "2-101".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/closed-world, so the description's job is to add what they can't: it discloses the 40,000-character windowing, that output is wrapped in a fence labeled as untrusted data, and that the text is an unofficial copy with a legal-reliance caveat. That is genuine behavioral context beyond structured fields, with only the pagination mechanics (next_offset) left to the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose and size limit, then the routing hint, then the trust/legal caveat. Nothing is redundant with the schema and no sentence could be dropped without losing a distinct piece of 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?

No output schema exists, yet the description explains the return shape (fenced untrusted text), the size bound, and the trust posture, while pagination fields are documented in the schema. An agent has everything needed to call this correctly and to treat the result safely.

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%, so the baseline is 3 and the schema already carries per-parameter meaning. The description adds the useful framing that citation lookup and title+section lookup are alternate modes, and supplies the canonical citation shape "1 V.I.C. § 254" that ties the two paths together.

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 (read) and resource (one section of the 2026 Virgin Islands Code) plus the two supported lookup modes and the 40,000-char window. An agent can immediately distinguish this from search_code, which finds sections rather than returning their text.

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?

"Use to read a section found by search_code" gives a clear entry condition and names the sibling that produces the input. It stops short of stated exclusions (e.g., don't use this to browse a whole title or to locate a section by topic), so the when-not half of the guidance is left implicit.

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