Skip to main content
Glama

Brick NJ Local directory

Search the directory

search_businesses
Read-onlyIdempotent

Search Brick NJ Local (1006 listings). All filters optional. place = town, city, neighbourhood or state as written ('Point Pleasant Beach', 'Austin, TX'). category = a name from list_categories. near_lat/near_lng sort by distance within radius_km.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
placeNo
queryNo
amenityNo
categoryNo
near_latNo
near_lngNo
open_nowNo
radius_kmNo
open_sundayNo
bookable_onlyNo
open_24_hoursNo
has_free_trialNo
contactable_onlyNo
max_monthly_priceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly/ idempotent/ non-destructive, so the safety profile is covered. The description adds genuine behavioral context: the 1006-listing corpus size, that filters combine optionally, and that near_lat/near_lng cause distance sorting bounded by radius_km rather than filtering. It says nothing about result ordering, pagination, or how the many boolean toggles (open_now, bookable_only, has_free_trial, contactable_only) interact or combine.

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?

The corpus size is front-loaded and every clause carries information; there is no filler. The telegraphic style ('place = town, city, neighbourhood or state as written') is dense but readable, though a little more structure would help with 15 parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter tool with no output schema, the description is thin: it never says what a result record contains, how results are ordered by default, or how max_monthly_price and the boolean filters constrain the set. An agent can call it correctly on the documented parameters but must guess at two-thirds of the surface.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 15 parameters, so the description carries the full burden and only partially discharges it. It clarifies place formats with examples ('Point Pleasant Beach', 'Austin, TX') and defines the geo-sort semantics of near_lat/near_lng/radius_km, but leaves query, limit, amenity, max_monthly_price and six boolean filters with no explanation beyond their names.

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?

'Search Brick NJ Local (1006 listings)' states a specific verb and resource and quantifies the corpus, which immediately tells an agent this is a directory search rather than a single-record fetch. It stops short of naming the boundary against get_business or list_places, so the distinction still requires inference.

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?

'All filters optional' is useful framing, and it explicitly routes the agent to list_categories for valid category names, which is real alternative-naming. However, there is no guidance on when to use this versus get_business (single lookup) or list_places, nor on what an empty query returns, leaving the main selection decision implied.

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