Skip to main content
Glama

Search the directory

search_businesses
Read-onlyIdempotent

Search Gyms NJ (3263 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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: near_lat/near_lng sort by distance and are bounded by radius_km. It omits how filters combine, what the default limit of 10 means for result volume, and whether results are paginated.

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 definition is compact and front-loaded with the core action and dataset size, then breaks filters into short labeled clauses. The listing count is a minor flourish but arguably useful scoping information; little else is wasted.

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

Completeness3/5

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

For a 15-parameter search tool with no output schema, the description covers the trickiest filters but not the return shape, result ordering when no coordinates are given, or how the boolean flags interact. It is workable but leaves an agent guessing on several non-obvious parameters.

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 0%, so the description must carry the load, and it only explains 4 of 15 parameters (place, category, near_lat/near_lng, radius_km) with useful detail such as the 'Austin, TX' format. The remaining eleven, including query, amenity, max_monthly_price and the boolean filters, are left to name inference.

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 names a specific verb and resource ('Search Gyms NJ (3263 listings)') and immediately scopes it to a directory of listings. It does not explicitly contrast with siblings like get_business or list_places, but the pointer to list_categories for the category filter partially anchors it in the tool family.

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' implies this is a broad discovery call, and 'category = a name from list_categories' gives a concrete prerequisite workflow. There is no explicit guidance on when to prefer get_business for a single known record or list_places for place lookups, so the when-not side is left to inference.

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