Skip to main content
Glama
Sign In

Spotby Business Registry

by io.spotby
OverviewDiscussionsAdmin

search_businesses

Search businesses in the Spotby registry with natural-language terms (what they do, services, needs) and/or a location. Results are ranked: any term can match, businesses covering more terms come first. Location matches the business address and also the areas the owner says they serve. Each result includes provenance (asserted_by: owner-maintained or imported from open data) and why it matched. Use get_business for full details.

Input Schema

NameRequiredDescriptionDefault
cityNoAlias of location
limitNo
queryNoNatural-language terms, any language (English or Italian work best), e.g. "24/7 emergency plumber blocked drains" or "gluten free trattoria"
categoryNoOptional. Exact filter only for Spotby keys: ristorazione (food and drink), negozio (shop), servizi (personal services), professionisti (professional services), artigiani (trades and crafts), ricettivita (accommodation). Any other value is treated as an extra search term.
industryNoOptional boost by industry the business serves (B2B): fashion, retail, food, hospitality, finance, healthcare, manufacturing, tech, realestate, services, nonprofit, public
locationNoCity, town or area, e.g. "Newcastle". Matches where the business is located or the areas it serves.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Filter by category key or label"New value: +"Optional. Exact filter only for Spotby keys: ristorazione (food and drink), negozio (shop), servizi (personal services), professionisti (professional services), artigiani (trades and crafts), ricettivita (accommodation). Any other value is treated as an extra search term."
    • changedInput schema / properties / city / description
      Previous value: -"Filter by city (partial match)"New value: +"Alias of location"
    • changedInput schema / properties / industry / description
      Previous value: -"Filter by served industry key: fashion, retail, food, hospitality, finance, healthcare, manufacturing, tech, realestate, services, nonprofit, public"New value: +"Optional boost by industry the business serves (B2B): fashion, retail, food, hospitality, finance, healthcare, manufacturing, tech, realestate, services, nonprofit, public"
    • addedInput schema / properties / location
      Added value: +{
+  "description": "City, town or area, e.g. \"Newcastle\". Matches where the business is located or the areas it serves.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Free-text search on business name and description"New value: +"Natural-language terms, any language (English or Italian work best), e.g. \"24/7 emergency plumber blocked drains\" or \"gluten free trattoria\""
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it explains ranking logic, that any term can match, that location matches both business address and served areas, and that results include provenance and match reasons. It does not mention authentication, rate limits, or pagination behavior.

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 front-loaded and efficient: it states the core search capability first, then ranking, location matching, provenance, and finally the sibling alternative. Every sentence adds useful information without redundancy.

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 6-parameter search tool with no required parameters, no output schema, and solid schema coverage, the description provides the key behavioral context an agent needs: ranking, location scope, result provenance, and where to go for full details.

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

Parameters3/5

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

Schema coverage is high (83%), so the schema already documents most parameters, including the specialized category and industry fields. The description adds useful semantic context for query and location matching, but does not elaborate on limit, category, or industry beyond the schema.

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: search businesses in the Spotby registry using natural-language terms and/or location. It also distinguishes the tool from its sibling by explicitly directing users to get_business for full details.

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 explains when to use this tool: for discovery via natural-language terms or location. It names get_business as the alternative for full details, but does not mention get_changes or give explicit when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Spotby Business Registry toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources