Skip to main content
Glama

Fox River Press

Find a state's official court records search

court_records_search
Read-onlyIdempotent

The official online court case search for a U.S. state or the District of Columbia: who runs it, what a member of the public can find there, and what it costs, each fact with the court page it was read from and the day it was read. Give a state's name or two-letter code, or omit it for every state. Federal cases are on PACER, not here.

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

Input Schema

NameRequiredDescriptionDefault
stateNoA state's name or two-letter postal code, for example Illinois or IL. Omit for every state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond the schema: every fact is paired with the court page it came from and the date it was read, which tells the agent this is a provenance-carrying informational lookup rather than raw case records. It does not discuss response size when omitting the state, which is the main residual gap.

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?

Three short sentences, front-loaded with what the tool returns and followed by the two operational instructions. The first sentence is dense with enumerated return items but every clause carries information; nothing is filler.

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?

For a one-optional-parameter, read-only lookup with no output schema, the description covers scope, output contents with provenance, and the invocation variants. It stops short of describing response shape or any limit when querying all states, a minor omission given low complexity.

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

Parameters3/5

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

There is a single optional parameter and schema description coverage is 100%, so the schema already explains the name-or-postal-code format and the omit-for-all behavior. The description restates both without adding format nuances (e.g., case sensitivity, ambiguous input handling), so the baseline 3 applies.

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 names a specific resource and scope: the official online court case search for a U.S. state or D.C., and enumerates what it returns (operator, what the public can find, cost, source citation, retrieval date). It also explicitly distinguishes the resource from federal coverage by noting that federal cases live on PACER, so an agent can tell what this tool is and is not.

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?

It gives explicit invocation guidance — supply a state name or two-letter code, or omit the parameter to get every state — and an explicit exclusion ('Federal cases are on PACER, not here'). It does not point to a specific alternative tool for federal lookups, but the exclusion is clear and none of the listed siblings appear to cover that case.

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