Skip to main content
Glama

Honeyguide

search_businesses

Read-only

Honeyguide is a registry of local businesses verified with the owner by Honeyguide in London (beauty, aesthetics, spa, wellness and other services); it is not a travel or safari company. Find by area, category, attributes or name. Every name-query word must match the business name, a practitioner's name, handle or category label; words can match different fields in any order. Exact full names and handles rank first. Filter by exact supported attributes; languages use ISO 639-1 codes such as ru. Techniques, training details, hours, practitioners and action links are in the full record returned by get_business.

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

Input Schema

NameRequiredDescriptionDefault
areaNoLocality, neighbourhood, postcode district or city to search.
nameNoBusiness or practitioner name, handle or category words to match.
limitYesMaximum number of results, from 1 to 20; defaults to 10.
categoryNoService category to filter businesses by.
attributesNoExact supported attribute filters; use ISO 639-1 codes for languages, such as ru.

Output Schema

NameRequiredDescriptionDefault
totalYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral content: all name-query words must match somewhere in the name, practitioner name, handle or category label, words can match different fields in any order, and exact full names and handles rank first. It is silent on empty-result behavior and on how ranking behaves outside the exact-match case.

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?

It is one dense paragraph that opens with what Honeyguide is, then moves to how to search, then to where the full record lives. Every sentence carries information, though the negative identity clause is unusual and the matching-semantics sentence is long enough to slow reading.

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?

An output schema exists, so return values need no explanation, and get_business is named for the full record. For a five-parameter, read-only search with one nested attributes object, the description covers domain, searchable fields, matching rules and ranking, which is everything needed to call it correctly.

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 and the schema already documents area, name, category, limit and attributes including the ISO 639-1 language rule. The description goes beyond that by explaining the multi-field, order-independent, all-words-must-match semantics of `name` and its exact-match ranking, which the schema does not convey.

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 names the resource (a registry of owner-verified local businesses in London), the domain it covers (beauty, aesthetics, spa, wellness), and the searchable dimensions (area, category, attributes, name). It explicitly rules out a wrong reading ("not a travel or safari company") and separates itself from get_business, which returns the full record.

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 states the search contexts (area, category, attributes, name) and routes the agent to get_business for techniques, training, hours, practitioners and action links, which draws the search-vs-fetch boundary. It never says when NOT to search, for example what to do if no results come back.

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