Skip to main content
Glama

As Titles

as_titles
Read-onlyIdempotent

List all 38 published titles of the American Samoa Code Annotated with their official names, e.g. Title 46 is Criminal Justice, Title 42 is Domestic Relations. Routing help for when you know the subject but not the title number, call this or as_search before guessing a citation. Keyless.

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": {},
    "name": "as_titles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description still adds real context beyond them: the fixed size of the result set (38 titles) and "Keyless," which tells the agent no authentication setup is required. It stops short of describing the per-title record shape, which keeps it off 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.

Conciseness5/5

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

Two sentences plus a one-word tag, front-loaded with the resource and count, then the routing rule, then the auth note. Nothing is redundant and the example pair is doing real disambiguation work rather than padding.

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 zero-parameter read-only index tool with an empty schema and no output schema, the description supplies everything an agent needs: what comes back (titles plus official names), how large the set is, when to route here, and that no key is needed. No meaningful gap remains.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline is 4. The description correctly implies it is a no-argument catalog call rather than leaving the agent wondering whether filtering inputs exist.

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 — list all 38 published titles of the American Samoa Code Annotated with their official names — and anchors it with concrete examples (Title 46 Criminal Justice, Title 42 Domestic Relations). The scope is unambiguous and clearly distinguishable from a statute-lookup sibling.

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 names the triggering situation ("when you know the subject but not the title number") and prescribes the correct order of operations: call this or as_search before guessing a citation. That is a genuine routing rule rather than a vague suggestion.

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.