Skip to main content
Glama
jimdawdy-hub

freecase-mcp

by jimdawdy-hub

search_statutes

Search U.S. statutes by citation or natural-language text. Filter by jurisdiction and limit results to find relevant sections.

Instructions

Search the Freecase statute corpus by citation or natural-language text.

Requires a Freecase connector key in the FREECASE_MCP_KEY environment variable; without one, this tool returns an error explaining how to set it.

Returns the query echoed back, counts, and a results array. Each result mirrors the Freecase API fields exactly (section_id, canonical_citation, jurisdiction, code_family, heading, status, snippet, match_type). Exact-citation hits are pinned above full-text hits, and current law floats above repealed/renumbered sections. Pass a result's section_id to get_statute to read the full section text.

Args: q: The search query (a citation or text — forwarded unchanged). jurisdiction: Statute jurisdiction to search within. limit: Maximum number of results (1-100; default 25).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesThe search query, forwarded to Freecase as-is: a statute citation (e.g. '625 ILCS 5/11-501') or natural-language text. Freecase handles citation vs. full-text detection server-side.
limitNoMaximum results to return (1-100). Defaults to 25.
jurisdictionNoStatute jurisdiction to search. 'all' or a state/federal code: il, us, mn, fl, nm, wi, ar, ga, ky, me, nc, nd, ri, tn, vt, wy (the launched set). If a jurisdiction is not yet launched, Freecase returns a message listing the ones that are.all

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses behavior: returns query echo, counts, results array with fields, sorting of exact-citation hits above full-text, and error handling for missing environment variable.

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?

The description is well-structured and front-loaded with purpose and requirements, but slightly verbose with extra detail on return fields that could be covered by output schema.

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?

Given the output schema exists, the description covers all necessary aspects: prerequisites, search behavior, parameter details, and result structure, making it complete for a search tool.

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 description adds meaning beyond the schema: for 'q' it explains forwarding and detection, for 'limit' default/range, and for 'jurisdiction' lists options and behavior for unlaunched ones.

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 'Search the Freecase statute corpus by citation or natural-language text,' specifying the verb 'search' and the resource 'statute corpus,' which distinguishes it from sibling tools like search_cases and get_statute.

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 explains the prerequisite (Freecase connector key) and provides context for when to use the tool. It does not explicitly say when not to use it, but the sibling context implies alternatives.

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/jimdawdy-hub/freecase-mcp'

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