Skip to main content
Glama

Top-rated businesses

top_businesses
Read-onlyIdempotent

Best-reviewed businesses in a country, optionally in one city and category (e.g. best restaurants in Lagos: country="NG", city="Lagos", category="restaurant").

Ranked by the share of reviewers who recommend the place, with a small prior so one review cannot top the list, blended with the 1-5 star average where reviewers gave one.

Args: country: ISO-3166 alpha-2 code, e.g. NG city: optional city name category: optional category, one of the values in the categories list limit: 1-25 results

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": {
      "country": "<country>"
    },
    "name": "top_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
limitNo
countryYes
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing the ranking algorithm — share of recommending reviewers, a prior so a single review cannot top the list, blended with the star average — which tells the agent why ordering looks the way it does and why sparse-review entries are suppressed. It does not mention pagination or what happens when city/category yields nothing.

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?

Front-loaded with purpose and ranking semantics, then an args block that maps cleanly onto the four parameters. The ranking sentence is longer than strictly necessary but each clause (prior, star blending) carries real behavioral information, so little is wasted.

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 four-parameter read-only discovery tool with no output schema, the definition covers the input side fully and explains the ordering logic. The remaining gap is the return shape — there is no output schema and the description does not say what fields a business entry contains (name, rank, score, review counts), which an agent may need for follow-up calls.

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 description coverage is 0%, so the description must carry the full burden, and it largely does: country is pinned to ISO-3166 alpha-2 with an example, city and category are marked optional, category is explicitly constrained to the values in the categories list, and limit is bounded to 1-25. The only omissions are the limit default (10, visible only in the schema) and any format expectation for city names.

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 resource and scope ("best-reviewed businesses in a country, optionally in one city and category") and goes further by explaining the ranking criterion. The verb is implicit (a ranked list) rather than explicit, and it never names search_businesses or get_business as the alternative, so an agent must infer the boundary itself.

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 worked example ("best restaurants in Lagos: country=\"NG\", city=\"Lagos\", category=\"restaurant\"") gives concrete usage context and implicitly signals this is a discovery/browse tool rather than a lookup. However there is no when-to-use/when-not guidance and no routing to search_businesses for keyword queries, so the selection decision against siblings is left to inference.

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