Skip to main content
Glama

Search estate planning firms

search_firms
Read-onlyIdempotent

Find listed estate planning firms by place (location text, state, metro, or lat/lng with a radius), service, whether the first step can be completed online, and whether the firm publishes a price. Results include each firm's profile URL and the source of every fact. Place searches list labeled sponsored placements first. Name-only nationwide lookup is alphabetical, not ranked.

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_firms"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude, with lng: search around a point instead of a named place.
lngNoLongitude, with lat.
nameNoPart of the firm name. Name-only lookup works without a place and sorts alphabetically. A trailing state, e.g. Sterling Hawaii, is parsed only if the literal name has no match; explicit geography is not overridden.
limitNoResults per page (default 20).
metroNoMetro slug from list_places, e.g. portland-or. An alternative to location.
stateNoState code or slug, e.g. OR or oregon. An alternative to location.
offsetNoPublic results to skip, for paging (maximum 40).
onlineNoOnly firms with online intake for the requested service. General estate planning excludes package-specific routes; contact and scheduling forms do not count. Read online_start for scope.
pricedNoOnly firms that publish a price.
serviceNoNarrow to firms that list this service on their website (see list_services).
locationNoCity and state ("Portland, OR"), a state ("Oregon" or "OR"), or a 5-digit ZIP code. Maui and Hawaii island aliases use disclosed reference points and the requested radius, not island boundaries. For search_firms, omit place only with a nonempty name; summarize_place may omit place for nationwide facts.
radius_miNoSearch radius in miles around a city, ZIP, metro or point (1–250, default 50). Ignored for states.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-obvious behavior: sponsored placements are labeled and listed first, name-only results are alphabetical rather than ranked, and every fact carries a source. It does not discuss paging limits or result-count behavior beyond what the schema states.

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 dense sentences, front-loaded with the capability and followed by result contents and ranking caveats. Every sentence carries information, though the final two clauses about sponsored placements and alphabetical ordering are compressed enough to require a second read.

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 twelve-parameter search tool with no output schema, the description covers what results contain (profile URL, fact sources) and how ordering works, which is the main thing an agent needs. Minor gaps remain around paging behavior and empty-result handling, but the schema covers the mechanics.

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%, so all twelve parameters are already documented, including the lat/lng pairing, radius defaults, and the name/state parsing rule. The description adds ranking semantics (sponsored-first, alphabetical) but no per-parameter meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Find listed estate planning firms") and enumerates the filter axes: place, service, online intake, published price. An agent can distinguish this from get_firm (single firm) and summarize_place (aggregate facts) without opening the schema.

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?

Gives clear operating context: place searches rank sponsored placements first, name-only nationwide lookup is alphabetical, and the schema notes place may be omitted only with a nonempty name. It stops short of explicitly naming when to prefer summarize_place or get_firm, so the alternative-routing guidance is implied rather than stated.

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