Skip to main content
Glama

BlooTrue business directory

Find businesses and their reviews

find_businesses
Read-onlyIdempotent

Finds businesses on BlooTrue from what the person asked for, in their words: what they need and what matters to them, plus the town or city if they named one (for example 'family dentist, gentle with kids, open Saturdays'). Use it when someone wants a business with real reviews, not for their own widgets. Read-only. Returns up to 24 a page with their BlooTrue page link, each review platform's own rating and count, and why they matched.

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
pageNoResult page, from 1.
queryYesWhat the person is looking for, in their words. Include the town or city only if they named one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/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 "Read-only" in the description is largely redundant. It does add real value by disclosing the return shape (up to 24 per page, page link, per-platform rating and count, match reason), but omits the page cap of 20 implied by the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose, then the routing condition, then the return summary in a logical order with no filler sentences. It is dense and slightly run-on in the opening clause, but every sentence carries 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?

For a two-parameter read tool with no output schema, the description covers what goes in, what comes back, and the page size, which is nearly everything an agent needs. The missing piece is the 20-page ceiling from the schema, which bounds total result volume.

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; the description earns a bump by showing a model query ("family dentist, gentle with kids, open Saturdays") and reinforcing that the town is included only if named. That example materially shapes how the free-text query should be composed, which the schema alone does not teach.

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?

Names a specific verb and resource ("Finds businesses on BlooTrue") and immediately scopes the input as the person's own words, with a concrete example. An agent knows exactly what this retrieves and in what form, not just that it searches.

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?

Gives an explicit when-to-use condition ("when someone wants a business with real reviews") and a when-not boundary ("not for their own widgets"). No sibling tools exist to name, so the absence of an alternative is acceptable, though "their own widgets" is an oddly vague exclusion.

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