Skip to main content
Glama

Find similar businesses

find_similar
Read-onlyIdempotent

Businesses like a given one: same industry, categories in common, nearby (same canton, then province) and the same signals (website, Instagram/TikTok, how they book, independent). Use it to grow a list from a business that worked. No credits; counts toward the daily search results; contacts are not shown.

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": {
      "code": "<code>"
    },
    "name": "find_similar"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesBusiness code to start from
limitNoHow many (max 50, default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond readOnly/idempotent/non-destructive annotations, the description discloses the match logic itself (shared industry, common categories, same signals), the geographic fallback order (same canton, then province), the cost profile (no credits but counted against daily search results), and an output restriction (contacts not returned). These are exactly the behavioral facts an agent could not get from the schema or annotations.

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?

Two dense sentences: the matching criteria are front-loaded and the quota/output caveats follow. Every clause carries information (match rules, fallback order, cost, exclusion) with no filler or repetition of the name.

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 flags that contacts are absent from results and that consumption is charged against daily search results, which is what an agent needs before committing. Remaining gaps are small (no statement of result ordering or what happens when the canton/province pool is empty), so it is near-complete rather than fully complete.

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 description coverage is 100%, with both parameters documented (the seed business code and the 1-50 limit with default 20). The description only says the seed is "a given one," adding no format, validation, or sizing guidance beyond the schema, so the baseline 3 applies.

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?

The description states a specific operation on a specific resource: find businesses resembling a given business, defined by industry, shared categories, proximity, and matching signals. An agent can tell this is a similarity/lookalike lookup rather than free-text search, though it never names search_businesses or another sibling to draw the contrast explicitly.

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 gives a concrete use case ("grow a list from a business that worked"), which implicitly positions it as an expansion/completion step rather than a first-pass discovery call. It does not state when not to use it or name an alternative for the initial discovery case, so the guidance is clear but not exhaustive.

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