Skip to main content
Glama

Honeyguide

get_business

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. Get a verified local business in London: grouped services, techniques, training, practitioners (who performs it), qualifications, languages, hours, related locations and Honeyguide action links, with verification dates. Records can be found by area, category, attributes or name through search_businesses. An unknown handle uses the same word matching and resolves only when one record matches; ambiguous matches return suggestions.

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

Input Schema

NameRequiredDescriptionDefault
slugYesBusiness handle returned by search_businesses.

Output Schema

NameRequiredDescriptionDefault
urlYes
areaYes
nameYes
slugYes
hoursYes
peopleNo
actionsYes
relatedNo
book_urlNo
categoryYes
servicesYes
attributesYes
updated_atYes
contact_urlNo
descriptionYes
hours_notesNo
published_atNo
location_typeYes
subcategoriesYes
owner_verifiedYes
schema_versionYes
verification_textYes
verified_by_owner_onYes

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 needs no restating. The description adds behavior beyond that: records carry verification dates with the owner, and an unrecognized slug triggers fuzzy word matching that either resolves to one record or returns suggestions instead of erroring. It does not describe failure modes for a slug with no near match, which is the remaining gap.

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?

Content is front-loaded correctly: what the registry is, what the record contains, then the search alternative and the unknown-handle rule. The opening sentence is dense, carrying the registry framing and the "not a travel or safari company" disclaimer, but that disclaimer does real disambiguation work. Minor tightening is possible, but nothing is pure padding.

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 the enumerated record contents are a bonus rather than a necessity, and no return-value documentation is owed. With one fully-described parameter, read-only annotations and an explicit sibling alternative plus fallback semantics, an agent has everything needed to call this 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 slug's format, length and pattern are already documented, and the baseline would be 3. The description earns an extra point by explaining how the slug is tolerated when it does not match exactly: word matching applies and ambiguity yields suggestions rather than a hard failure. That is behavioral meaning about the parameter that the schema cannot express.

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 ("Get a verified local business in London") and enumerates the record contents: grouped services, techniques, training, practitioners, qualifications, languages, hours, related locations, verification dates. It also explicitly disclaims what the tool is not ("not a travel or safari company"), which disambiguates a name that could be misread, and names the sibling search_businesses as the discovery path.

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 routes the agent: discovery by area, category, attributes or name belongs to search_businesses, so this tool is for a known handle. It also states the fallback rule for an unknown handle (same word matching, resolves only on a single match, ambiguous matches return suggestions). It stops short of an explicit "use this when you already have a slug from a prior search" sentence, so the selection rule is strongly implied rather than stated outright.

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