MCP server for legal data including court records, case law, legal filings, and regulatory information for AI agents.
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.
Average 4.2/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion or overlap between tools.
A single tool's name follows a clear verb_noun pattern ('search_court_records'), which is consistent.
One tool for the broad domain of legal and court records is severely insufficient; a typical server would require multiple tools for different operations (e.g., case details, filings, court listings).
The single search tool covers only basic search by name, case number, or state. Missing CRUD operations, detailed case retrieval, and other essential functionalities for the domain.
search_court_recordsASearch 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') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint. The description adds value by detailing return fields (parties, case type, filing date, judgment, docket number) and confirming it searches only public records. No contradictions; the description enriches behavioral context.
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?
The description is three concise sentences: first states the core purpose and search criteria, second lists return fields, third gives use cases and limitation. No redundant or extraneous content; front-loaded with essential information.
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?
Given the tool's complexity (3 optional parameters, no output schema, read-only search), the description adequately covers purpose, return values, use cases, and constraints. It could mention pagination or result limits, but current content is sufficient for correct invocation.
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?
Schema description coverage is 100%, so the component schema already describes all three parameters. The description repeats the search criteria (name, state, case number) but adds no new semantic meaning beyond the schema. Baseline score of 3 is appropriate.
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?
The description clearly states the tool searches public court records by name, case number, or state, specifies returned data (parties, case type, filing date, judgment, docket number), and lists use cases. The verb 'search' and resource 'public court records' are specific, and the absence of siblings makes differentiation unnecessary.
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?
The description explicitly states use cases: 'background checks, legal research, or case tracking' and notes the limitation 'limited to public records.' It provides clear context for appropriate use, though it does not include explicit when-not-to-use or alternatives.
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.
No comments yet. Be the first to start the discussion!
