Skip to main content
Glama

Point Pleasant Local directory

Search the directory

search_businesses
Read-onlyIdempotent

Search Point Pleasant Local (748 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

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, closed-world behaviour, so the safety profile is covered. The description adds useful behavioural detail about geo sorting ('sort by distance within radius_km') but says nothing about default ordering when no location is supplied, pagination, or result shape. It adds some value without fully profiling behaviour.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very front-loaded: the tool's identity and dataset size come first, then the 'all filters optional' fact, then only the non-obvious parameters get sentences. Notation like 'place = ...' is compact and there is no filler.

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, zero-required search tool with no output schema, the description leaves meaningful gaps: what a result contains, how limit/pagination behaves, whether filters AND together or intersect, and whether near_lat requires near_lng. The covered pieces are good, but the definition is not sufficient on its own.

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 0% across 15 parameters, so the description must compensate, and it does so for the hardest ones: the place string format with concrete examples, the category source, and how near_lat/near_lng interact with radius_km. However, 10 parameters remain unexplained, including domain-specific ones like contactable_only, bookable_only, and max_monthly_price, so compensation is only partial.

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 opens with a specific verb and resource, 'Search Point Pleasant Local (748 listings)', and previews the search dimensions (place, category, geo). It does not explicitly distinguish itself from siblings like list_places or get_business, which keeps it from a 5.

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' plus 'category = a name from list_categories' gives real operational guidance and routes the agent to a sibling for category values. There is still no statement of when to prefer this tool over list_places or get_business, 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