Skip to main content
Glama

Search law firms by name

search_law_firms
Read-onlyIdempotent

Law firms and agents whose name matches, best first. Each result carries its PERM record and the slug that the get endpoint takes. Example: {"q":"fragomen"}.

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": {
      "q": "<q>"
    },
    "name": "search_law_firms"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes2 to 120 characters of the name. Example: fragomen.
limitNoResults to return, 1 to 100. 10 when left out. Example: 25.

Output Schema

NameRequiredDescriptionDefault
asOfYesThe date the data is true for, YYYY-MM-DD, when one applies.
dataYesThe answer, or found: false when no record matched.
pageYesThe page on permtracker.app that shows the same thing. Cite it.
sourceYesWho published the underlying records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine value with result ordering ('best first') and result contents (PERM record plus slug), but does not say whether matching is prefix, substring, or fuzzy, nor how many results to expect by default.

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, front-loaded clauses: what matches, ordering, and payload. The trailing JSON example largely restates the schema's own example for q, so it is mild redundancy rather than wasted space.

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 two-parameter read tool with a full output schema and rich annotations, this covers purpose, ordering, and the search-to-get handoff. The remaining gaps (matching semantics, follow-up naming) are small but real.

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%, with both q (2-120 chars) and limit (1-100, default 10) fully documented, so baseline is 3. The description's 'name matches' phrasing adds the useful nuance that q is a partial-match term rather than an exact name, but adds nothing about limit or ranking tradeoffs.

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?

The description states a specific behavior: name-matching lookup of law firms and agents, ranked best-first, with each result carrying its PERM record and the slug consumed by the get endpoint. That slug note implicitly separates it from get_law_firm, though the sibling is never named.

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

Usage Guidelines3/5

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

Usage is only implied: the mention that results carry 'the slug that the get endpoint takes' hints at a search-then-get workflow, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer the routing itself.

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.