Skip to main content
Glama

EstatePlan.now

Summarize a place

summarize_place
Read-onlyIdempotent

The facts about estate planning firms in one place, in one call: how many are listed and reviewed, how many publish a price and the lowest and highest published amounts (each named with its firm, package and scope; never an average), which firms let you begin online, which services firms list, when records were checked, and ready answers to common questions such as "How much does an estate plan cost near Portland?".

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

Input Schema

NameRequiredDescriptionDefault
latNoLatitude, with lng: search around a point instead of a named place.
lngNoLongitude, with lat.
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.
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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety bar is low. The description nonetheless adds genuinely behavioral detail: prices are the lowest and highest published amounts, each attributed to a firm/package/scope, and explicitly 'never an average' — a meaningful disclosure about how figures are computed.

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?

One dense but well-structured sentence, front-loaded with the core value proposition ('in one place, in one call') followed by the inventory of returned facts. No filler, though the mid-sentence parenthetical about price attribution is heavy.

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 no output schema, the description does the right work by enumerating the return payload in detail. For a read-only aggregate tool with six fully documented optional parameters, this is close to complete; only the routing versus sibling tools is left 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 coverage is 100% and every parameter (lat/lng, metro, state, location, radius_mi) is already documented in the schema, including aliases and the nationwide-omission rule. The description adds nothing about parameter behavior, so the baseline 3 applies.

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 resource (estate planning firms in a place) and enumerates what the summary contains: counts, published price range with firm/package/scope, online-start availability, listed services, and record-check dates. That is clearly distinguishable from a firm-listing tool, though it never names a sibling to contrast with.

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: 'in one call' and 'ready answers to common questions such as "How much does an estate plan cost near Portland?"' suggest the aggregate/overview case. There is no explicit statement of when to prefer this over search_firms or get_firm, and no exclusions.

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