Skip to main content
Glama

SuVerse

A business by its name

find_business
Read-only

One business the user NAMED, matched by its name near location (default radius 15 miles); typos, word order and punctuation are tolerated. Not in the catalogue → name_not_found, and up to 5 nearby businesses that carry the name's distinctive word (never presented as the business asked for). intent, query, needed_by, deliver_to shape the short card the same way as list_cards. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.

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": {
      "name": "<name>"
    },
    "name": "find_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesthe business name as the user said it
queryNothe thing under the task («red roses», «ribeye»): picks the ≤ 5 items on the card
intentNowhat the user means to do with this business
locationNoa postcode, a city or "lat,lng" — orders the matches by nearness and bounds the nearby list
needed_byNowhen: «sunday», «tomorrow 19:00», «now», «tomorrow after 15:00» — read on the business’s own clock, three ways (on_day / open_at / slot_after)
deliver_toNowhere it must be brought (a postcode is best): the card says confirmed / refuted / unknown
radius_milesNoDefault 15 (the same in every tool).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses fuzzy matching tolerance, the name_not_found fallback, the limit of up to 5 nearby suggestions, and that suggestions are never presented as the requested business. It also reinforces that results are candidates and no booking, ordering, or payment occurs without user permission.

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?

The description is dense but front-loaded: it states the core matching behavior first, then the fallback, then parameter/card semantics, then safety constraints. Every sentence adds relevant operational context without unnecessary repetition.

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

Completeness5/5

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

For a 7-parameter read-only lookup tool with no output schema, the definition covers purpose, fuzzy matching, fallback behavior, parameter effects, and safety boundaries. The annotations already establish read-only safety, and the description supplies the remaining behavioral context an agent needs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by explaining that intent, query, needed_by, and deliver_to shape the short card the same way as list_cards. It also clarifies fuzzy name matching and the default radius behavior for location.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description states a specific verb and resource: finding one named business by its name near a location. It also distinguishes this from broad catalog search by emphasizing the user NAMED the business and describes fuzzy matching and fallback behavior.

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?

It clearly implies use when the user has named a business and describes what happens if that name is not in the catalogue. It does not explicitly contrast with get_business or search_catalog, so the alternative-selection guidance is present but not exhaustive.

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.