Skip to main content
Glama

search_courts

Read-only

Search the 1Court Directory by county or state name, courthouse name, city, or phone number. Returns matching counties and courthouses with their 1Court page URLs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_courts"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA county, state, courthouse name, city or phone number, e.g. "Maricopa", "Van Nuys courthouse", "Jersey City", "201-748-0156"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"A county or state name, e.g. \"Maricopa\", \"Cook County\", or \"Nevada\""New value: +"A county, state, courthouse name, city or phone number, e.g. \"Maricopa\", \"Van Nuys courthouse\", \"Jersey City\", \"201-748-0156\""
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds that results are 'matching counties and courthouses with their 1Court page URLs,' which is genuinely useful return-shape context given there is no output schema. It stops short of stating result limits, pagination, or empty-match behavior.

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?

Two tight sentences: the first front-loads what is searched and by which keys, the second states what comes back. No filler, no repetition, and the most decision-relevant information leads.

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-parameter read-only lookup with full schema coverage and annotations, the description covers purpose, inputs, and return contents adequately. The only real gap is sibling disambiguation, which matters here because get_court_info and list_counties overlap with this tool's territory.

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?

Schema coverage is 100% and the single parameter is already documented with examples, so the schema does the heavy lifting. The description restates the same accepted query types without adding syntax, matching rules, or precedence (e.g., whether 'Maricopa' matches county or city first), so it lands at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search the 1Court Directory') plus the exact lookup keys (county/state, courthouse name, city, phone). It does not, however, distinguish itself from overlapping siblings such as get_court_info, list_counties, or list_states, so an agent cannot tell from the description alone which to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does but never says when to use it instead of list_counties (enumeration) or get_court_info (detail lookup). No prerequisites, exclusions, or alternative routing are given; the agent must infer usage from the listed query types.

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