Skip to main content
Glama

Yeow business index

search_businesses

Search US businesses and nonprofits by text, category, city, state. Public business facts only, with a source on every field. Free in preview.

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
qNo
cityNo
limitNo
stateNo2-letter code
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose useful traits — public-data scope and per-field source attribution, plus a 'free in preview' commercial note — but it says nothing about result ordering, pagination, the meaning of limit, what happens with zero matches, or rate limits.

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?

Two tight sentences, filters front-loaded, with the coverage/source guarantee and cost note appended. No redundant phrasing and nothing that restates the tool name idly.

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 five-parameter search tool with no annotations and no output schema, the definition covers what data is returned at a high level (public facts with sources) but omits result-set behavior and limit semantics. Adequate to call, not sufficient to predict results confidently.

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 only 20% (only 'state' is documented), so the description must compensate. It names the four filter dimensions (text/category/city/state), which maps roughly to q/category/city/state and adds marginal meaning, but leaves 'limit' entirely unaddressed and gives no format hints for q or category.

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 concrete verb ('Search') with the resource ('US businesses and nonprofits') and the searchable facets (text, category, city, state). The verb contrasts naturally with the sibling get_business, though the description never names that sibling to sharpen the distinction.

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 implied by the facets listed and the note that results are public facts only, but there is no explicit when-to-use/when-not guidance and no routing to get_business for a single-record lookup. An agent must infer the boundary from the verbs alone.

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