Skip to main content
Glama

1Network local business directory (read-only)

Search businesses

search_businesses
Read-onlyIdempotent

Search the 1network directory of US local businesses by category, place, rating, open now and "accepts requests". Free. Returns at most 25 businesses a page with their public phone and website, labelled sponsored or featured when paid. Use accepts_requests true to find the businesses that request_quotes can reach.

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
qNoWords in the business name.
latNoLatitude, with lng and radius_miles to search around a point.
lngNoLongitude.
zipNo5-digit ZIP code.
cityNoCity name (use with state).
limitNoHow many results (1 to 25, default 10; 10 a page without an API key).
stateNo2-letter US state code.
cursorNonext_cursor from the previous page.
categoryNoCategory slug or name from list_categories, for example "plumbers".
open_nowNoOnly businesses open right now.
directoryNoLimit to one industry directory's categories. One of: auto, childcare, cleaning, dentists, electricians, fitness, hvac, lawn, lawyers, med-spa, pets, plumbers, remodelers, restoration, salons, senior-care, tax-finance, therapists, weddings, wellness.
min_ratingNoOnly businesses rated at least this many stars.
radius_milesNoSearch radius in miles around lat/lng or the ZIP code.
accepts_requestsNotrue: only businesses that accept quote requests from AI assistants (the ones request_quotes can reach).

Output Schema

NameRequiredDescriptionDefault
shownYes
filtersYes
businessesYesAt most 25 businesses. Paid placement is labelled with sponsored and featured.
next_cursorNo
accepting_requestsYesHow many of the shown businesses accept AI requests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 description earns credit for adding cost ('Free'), page size ('at most 25 businesses a page'), returned fields (public phone and website), and monetization labelling (sponsored or featured when paid). It does not explain cursor expiry or what happens with zero filters, which keeps it below 5.

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?

Four short sentences with no filler: purpose first, then cost, then result shape, then the one non-obvious usage tip. Even the one-word sentence 'Free.' carries decision-relevant information.

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 14 optional parameters, an output schema, and full annotation coverage, the description covers purpose, cost, page size, and the key filter linkage. The main gap is that it never says what a call with no filters returns, which matters given zero required 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 coverage is 100% and every parameter, including accepts_requests, cursor, directory, and radius_miles, is already described in the schema. The description's restatement of accepts_requests and its filter list add little 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search the 1network directory of US local businesses') and enumerates the filter families (category, place, rating, open now, accepts requests), which is far more specific than the title. It does not name a sibling such as count_businesses to contrast scope, so it stops short of 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit, actionable condition: use accepts_requests=true to find businesses that request_quotes can reach, which ties this tool to a downstream workflow. It gives no exclusions or alternative routing (e.g., when to use count_businesses instead of this for totals), so it is clear context without full when-not guidance.

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