Skip to main content
Glama

Find businesses

find_businesses
Read-onlyIdempotent

Finds Gwiksoft businesses that sell what the customer is looking for, optionally in a city, with a few matching products from each. Each result’s business id works with the other tools. Online stores deliver beyond their city.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "find_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoA city, e.g. "Hyderabad", to keep to businesses there and online stores.
queryYesWhat the customer wants, e.g. "lab-grown diamond ring" or "wall-hung basin". Empty lists businesses.

Output Schema

NameRequiredDescriptionDefault
noteNo
businessesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world safety. The description adds genuine behavioral context beyond them: results carry a few matching products, the returned business id is usable with the other tools (enabling chaining), and online stores deliver beyond their city, which explains a non-obvious filter effect.

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?

Three short sentences, front-loaded with the core purpose, then the result shape and chaining hint, then the delivery nuance. Every sentence carries information an agent would otherwise have to guess.

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 an output schema present, the description need not explain return values, and it still offers the useful detail that results include a few products and interoperable ids. The one gap is sibling differentiation against search_products and get_business, which would complete the selection picture.

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 both parameters are documented in the schema, including the empty-query behavior, so the baseline is 3. The description adds only a little meaning on top, mainly the city/online-store interaction, without format or syntax detail.

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 verb+resource is concrete ('Finds Gwiksoft businesses') and the description adds the matching criterion ('that sell what the customer is looking for') plus what comes back ('a few matching products from each'). It does not explicitly distinguish itself from siblings such as search_products, so an agent must infer the business-first vs product-first split.

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 rather than stated: this is the discovery tool for businesses, and city is described as optional. There is no explicit when-not or named alternative (e.g., use search_products when the customer wants products across sellers), so the routing decision 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