Legal & Court Records MCP Server
Server Details
MCP server for legal data including court records, case law, legal filings, and regulatory information for AI agents.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 2.6/5 across 1 of 1 tools scored.
With only one tool in the set, there is zero risk of overlap or misselection between tools. The single tool's purpose is clearly defined with no ambiguity.
The single tool follows a clear verb_noun pattern (search_court_records) using snake_case. With only one tool, there are no competing conventions or inconsistencies to evaluate.
The server name 'Legal & Court Records MCP Server' implies a broad domain requiring multiple operations (retrieve, list, download, etc.), but contains only one search tool. A single tool is insufficient for this apparent scope.
The surface provides search functionality but lacks essential lifecycle operations for court records, such as retrieving case details, accessing documents, or filtering results. This creates significant gaps that will cause agent failures for common legal research workflows.
Available Tools
1 toolsearch_court_recordsCRead-onlyInspect
Search public court records database by individual name, case number, or state jurisdiction. Returns case details including parties involved, case type (civil/criminal), filing date, judgment, and docket number. Use for background checks, legal research, or case tracking. Limited to public records.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Full name or partial name of person involved in case (e.g. 'John Smith', 'Jane Doe') | |
| state | No | U.S. state or jurisdiction for search (e.g. 'CA', 'NY', 'Texas') | |
| case_number | No | Case identifier/docket number if known (e.g. '2023-CV-001234') |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description fails to disclose critical behavioral aspects such as data coverage limitations, rate limits, privacy restrictions, or what constitutes 'public' records.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
While appropriately brief, the single-sentence structure is overly terse given the information deficit in schema and annotations; key details are omitted due to excessive brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Severely incomplete given the absence of an output schema; the description fails to explain return value structure, result limits, or error conditions (e.g., no records found vs. API failure).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Given 0% schema description coverage, the description inadequately compensates by omitting format specifications (e.g., 2-letter state codes vs. full names), wildcard support, or parameter interdependencies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool searches public court records and identifies the three search dimensions, though it lacks specificity about jurisdiction scope (federal vs. state) or record types (civil vs. criminal).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides no guidance on when to use this tool versus alternatives, or how to combine parameters (e.g., whether name + state is required vs. case_number alone).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!