Skip to main content
Glama

As Statute

as_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the American Samoa Code Annotated (A.S.C.A.) by citation, e.g. "46.3502" (Murder in the 1st degree) or "1.0201" (laws applicable in American Samoa). Accepts "46.3502", "A.S.C.A. section 46.3502", "ASCA 46-3502", or "Title 46, Section 3502". Returns the current statutory text, its chapter, any amendment "History:" citation, and any "Case Notes:" (case-law annotations) asbar.org publishes for that section. Keyless. Use for "what does A.S.C.A. 46.3502 say", "American Samoa murder statute", or to check an American Samoa statute a case or contract relies on.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "citation": "46.3502"
    },
    "name": "as_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesSection citation as title.section, e.g. "46.3502" or "1.0201". The title is the part before the first separator.

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?

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered; the description adds genuinely new context by disclosing what is returned (statutory text, chapter, amendment History, Case Notes) and that access is keyless. It does not cover failure behavior for an invalid citation, keeping it below a 5.

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 the core action and resource, followed by format examples and return contents; every sentence carries information. It is dense and parenthetical-heavy, which slightly slows scanning, but no sentence 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?

A single-parameter, no-output-schema tool, and the description covers invocation formats, authentication (keyless), and the shape of the returned data including History and Case Notes. Nothing material an agent needs to call it correctly is missing.

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 description earns above that by enumerating accepted citation shapes ('A.S.C.A. section 46.3502', 'ASCA 46-3502', 'Title 46, Section 3502') that the schema's stricter 'title.section' wording does not convey. This tells the agent the parser is flexible rather than exact-format-only.

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 ('Get the FULL TEXT of a section of the American Samoa Code Annotated') with a concrete citation example, which cleanly distinguishes this lookup tool from a keyword-search sibling. An agent can tell immediately this is a fetch-by-citation tool, not a search tool.

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?

Gives explicit use-case triggers ('what does A.S.C.A. 46.3502 say', 'American Samoa murder statute', verifying a statute a case or contract relies on), which is clear context for when to call it. It stops short of stating when not to use it, but the citation-in/citation-out framing makes the boundary against search tools reasonably evident.

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.