Skip to main content
Glama

Orbtown business directory

search_businesses

Search companies listed in Orbtown. All given filters apply together (AND). Free text matches company or project name, website, trade, services, city, country and description, ignoring case and accents; exact name matches rank first. Returns name, services, website, address, country, profile link, total and a relevance score. Page with offset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity or part of the address, as the company wrote it, e.g. "Split"
limitNoResults per page, default 10
queryNoFree text: company or project name, website, trade or service, optionally with a city, e.g. "Limontera", "hopa.hr" or "Zahnarzt Graz"
offsetNoNumber of results to skip, for paging
countryNoISO 3166-1 alpha-2 code or country name, e.g. "AT" or "Austria"
categoryNoTrade id or trade name in English, German, Czech, Slovak or Polish, or part of it, e.g. "acc", "Accounting & tax", "dentist"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Trade id or trade name in English, German, Czech or Slovak, or part of it, e.g. \"acc\", \"Accounting & tax\", \"dentist\""New value: +"Trade id or trade name in English, German, Czech, Slovak or Polish, or part of it, e.g. \"acc\", \"Accounting & tax\", \"dentist\""
  2. Changed5 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Trade id or English trade name, e.g. \"acc\" or \"Accounting & tax\""New value: +"Trade id or trade name in English, German, Czech or Slovak, or part of it, e.g. \"acc\", \"Accounting & tax\", \"dentist\""
    • changedInput schema / properties / country / description
      Previous value: -"ISO 3166-1 alpha-2 code, e.g. \"AT\""New value: +"ISO 3166-1 alpha-2 code or country name, e.g. \"AT\" or \"Austria\""
    • addedInput schema / properties / limit / description
      Added value: +"Results per page, default 10"
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Number of results to skip, for paging",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Free text: company name"New value: +"Free text: company or project name, website, trade or service, optionally with a city, e.g. \"Limontera\", \"hopa.hr\" or \"Zahnarzt Graz\""
  3. First observed

TDQS

A3.9/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 burden and does well: it discloses which fields free text searches, that matching ignores case and accents, that exact name matches rank first, what fields are returned, and that results are paged by offset. It omits authorization needs, rate limits, or total-count behavior beyond the returned 'total' field.

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?

Three dense sentences, front-loaded with purpose then filter semantics then return/paging. Every clause carries information an agent needs; nothing is padding.

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 six-parameter, zero-required search tool with no output schema, the description supplies return fields and pagination, which is what an agent needs to call and consume it. It could still say that omitting all parameters returns an unfiltered list and note the default page size, but the gaps are minor.

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 adds genuine meaning on top by explaining that filters are ANDed, that `query` spans company/project name, website, trade, services, city, country and description, and that relevance ranking favors exact name matches. The offset paging note is redundant with the schema but harmless.

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?

States a specific verb and resource ('Search companies listed in Orbtown') plus the filter semantics ('All given filters apply together (AND)'), so an agent knows exactly what the tool does. No sibling tools exist to differentiate against, so the ceiling is 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains how filters combine and what free text covers, which is implied usage guidance for constructing a call. It never states when to prefer this over another approach or any precondition (e.g. that all parameters are optional and an empty call lists everything).

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