Skip to main content
Glama

Search businesses

search_businesses
Read-onlyIdempotent

Search Afefehub for reviewed businesses by name, dish, product, service or area.

Args: query: free text, e.g. "suya", "Mama Cass", "braids Lekki" country: optional ISO-3166 alpha-2 code, e.g. NG, GH, KE city: optional city or area; only businesses in it, e.g. Lagos or Lekki category: optional category, one of the values in the categories list limit: 1-20 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": {
      "query": "<query>"
    },
    "name": "search_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
limitNo
queryYes
countryNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 no behavior beyond that — no indication of result ordering, whether results are paginated beyond 'limit', or what happens when no match is found. For a read-only search the remaining gap is modest, so a 3 fits.

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?

Purpose is front-loaded in one sentence, followed by an explicit args block that maps one-to-one to the parameters with examples rather than prose. The 'Args:' formatting is slightly mechanical but adds no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, no schema descriptions, and no output schema, the definition covers inputs well but stops short of describing what comes back (fields per business, whether ranking or relevance order applies, pagination past the limit cap). An agent can invoke it correctly but cannot predict the response shape.

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 carries the full burden and largely meets it: it supplies intent for query, the ISO-3166 alpha-2 format for country, area scope for city, a 1-20 bound for limit, and value guidance for category. The category hint ('one of the values in the categories list') points at an external list that isn't resolvable from this definition, which keeps it from a 5.

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 gives a specific verb and resource ("Search Afefehub for reviewed businesses") plus the fields the query matches (name, dish, product, service, area), which tells an agent this is a free-text discovery tool. It doesn't explicitly contrast itself with siblings like get_business or top_businesses, relying on the agent to infer the difference.

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?

Usage is implied rather than stated: 'query: free text' and 'city: only businesses in it' hint at filtering composition, but there is no explicit when-to-use versus get_business or top_businesses. No prerequisites, exclusions, or fallback behavior are given.

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