Skip to main content
Glama

Belline Connect

Search businesses

search_businesses
Read-onlyIdempotent

Find local businesses that let AI assistants book through Belline. Matches words against the business name, trade, services and address as text; it does not search by distance. Returns each business with its services and price ranges, in its own currency. Only businesses whose owner switched this on are listed.

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 to match, for example 'plumber Marina'. Optional.
langNoLanguage code the business speaks, for example de or en. Optional.
limitNo
tradeNoA trade key as it appears in a business result (tradeKey), for example trades. Optional; when absent, the words in q are matched on their own.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: results are text-matched only, include services and price ranges in the business's own currency, and exclude businesses whose owner did not enable the feature.

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 matching semantics, then result shape and the opt-in filter. Nothing is repeated from the title and no sentence is filler.

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 no output schema, the description usefully explains the return shape (each business with services and price ranges, in its own currency). The remaining gap is pagination/limit behavior and result ordering, which an agent would need to interpret a capped result set.

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 75%, with limit carrying no description. The description compensates by explaining what q is matched against (name, trade, services, address) and what happens when trade is omitted, which is meaning beyond the schema's example strings.

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 (find local businesses) plus the platform scope (bookable through Belline) and the matching basis (name, trade, services, address as text). It clearly is a discovery tool, distinct from profile-fetching siblings, though it never names a sibling to contrast with.

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 does not search by distance" is an explicit when-not constraint that steers the agent away from proximity queries, and the note that only opted-in businesses are listed sets expectations about result coverage. What is missing is any routing statement versus alternatives such as get_business_profile or ask_business for an already-known business.

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