Skip to main content
Glama
Vaquill-AI

Vaquill-AI/vaquill-mcp

Official

search_us_statutes

Search the United States Code and Code of Federal Regulations by natural language query. Filter by title or corpus type to find federal statutes and regulations.

Instructions

Semantic search across the United States Code (USC) and Code of Federal Regulations (CFR). Use for federal statutory and regulatory questions: SEC (Title 17), FDA (Title 21), civil rights (Title 42), tax (Title 26), etc. Filter by corpusType ('USC' | 'CFR') and titleNumber. Returns sections with citation, title hierarchy, HTML/PDF/XML links. The returned act_id (e.g. 'USC_T42_C21_S1983') feeds get_us_statute_section_text for full text. Cost: 2 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query in natural language.
corpusTypeNoRestrict to one corpus. One of: `USC` (United States Code), `CFR` (Code of Federal Regulations), `STATE` (state statutes — 41 states currently ingested), `CONSTITUTION` (U.S. Constitution), `FEDERAL_RULES` (FRCP / FRCrP / FRE / FRAP / FRBP), `STATE_CONSTITUTION` (state constitutions, currently CA/VA/NC/WI), `STATE_RULES` (state court rules, currently CA), `EXECUTIVE_ACTION` (Federal Register Presidential Documents). Omit to search across all corpora.
stateNo2-letter state code (lowercase, e.g. `ca`, `tx`, `ny`) used to filter state corpora. Ignored when `corpusType` is `USC`, `CFR`, `CONSTITUTION`, `FEDERAL_RULES`, or `EXECUTIVE_ACTION`.
titleNumberNoFilter by USC/CFR title number (e.g., 17 for SEC, 42 for civil rights). Only meaningful for `USC`/`CFR`; ignored for state corpora whose titles are alphabetic (e.g. Texas `pe` = Penal Code).
limitNoNumber of results to return.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations exist, so the description carries full burden. It discloses semantic search nature, output contents, and result usage. It does not cover rate limits or auth, but is sufficient for a read-only search tool.

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?

Five well-structured sentences cover purpose, examples, filtering, output, and cross-tool usage. No redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given complexity of multiple corpora and filters, the description is nearly complete. Output schema exists, so return details are not needed. Cost and cross-tool link are valuable extras.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds little value and is misleading by limiting corpusType to USC/CFR while schema includes more options. It does not clarify other parameters beyond the schema.

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?

The description clearly states the tool performs semantic search across USC and CFR, with specific examples of titles and filtering. It distinguishes itself from sibling tools like get_us_statute_section_text by explaining the role of act_id.

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?

The description advises use for federal statutory/regulatory questions and provides filter guidance. It mentions cost and linking to another tool, but does not explicitly contrast with similar search tools like search_legislation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vaquill-AI/vaquill-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server