Skip to main content
Glama

Search attorneys

search_attorneys
Read-onlyIdempotent

List attorneys by name, firm, side and district, most cases first. get_attorney gives one attorney in full.

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

Input Schema

NameRequiredDescriptionDefault
nameNoPart of the name, any case.
sideNoOnly those with cases for this side, ranked by their cases on that side rather than by all their cases.
limitNoResults per page, at most 50 (the default).
cursorNonextCursor from the previous page; omit for the first page.
purposeNoOne sentence on what you are trying to find out. Logged to improve the dataset; never returned.
districtNoJudicial district, e.g. HARTFORD JD.
firm_juris_numberNoJuris number of their firm.

Output Schema

NameRequiredDescriptionDefault
totalYesMatches across all pages.
resultsYesThis page of matches.
nextCursorYesPass as cursor for the next page; null on the last.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so safety needs no restating. The description adds the ranking behavior (most cases first), which is genuinely useful, but says nothing about paging, result-set size, or empty-result behavior beyond what the schema carries.

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 short sentences, front-loaded with what it does then the disambiguation pointer. Nothing redundant, nothing padded.

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?

With an output schema, full parameter documentation, and complete annotations, the description covers what is needed to select and call the tool. Only paging expectations (cursor/limit cycling) are left entirely implicit.

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 description coverage is 100% and the schema descriptions are richer than the summary (e.g., side explains re-ranking by cases on that side). The description merely enumerates a subset of facets, adding no semantics beyond the schema.

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?

Specific verb and resource ("List attorneys") plus the filterable facets and the ranking order ("most cases first"). It also names the sibling get_attorney so the agent can tell list-of vs. single-record apart without opening schemas.

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?

"get_attorney gives one attorney in full" establishes the split: use this to enumerate/filter, use the sibling for full detail. No explicit when-not-to-use or mention of search_cases/search_firms as alternative entry points, so it stops short of a 5.

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