Skip to main content
Glama

Get business reviews

get_business
Read-onlyIdempotent

Summary and every review of one business on Afefehub.

Args: business: the business url (https://afefehub.com/b/...), its slug, or its business_id

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": {
      "business": "<business>"
    },
    "name": "get_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
businessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds nothing about result volume or ordering despite promising 'every review' (a potentially large, possibly paginated payload), which is the one behavioral trait that would genuinely help.

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?

Two short blocks, front-loaded with the purpose followed by the parameter, with no filler. The 'Args:' formatting is slightly Python-docstring mechanical but costs almost nothing.

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 one-parameter read-only fetch with no output schema and strong annotations, the definition covers purpose, identifier formats, and scope. The remaining gap — whether the 'every review' payload is truncated or paginated — is minor but real for a tool that could return unbounded results.

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% and the schema offers only a bare 'business' string, so the description carries the burden. It does so well by enumerating three accepted identifier forms — full URL, slug, or business_id — which an agent could not guess from the schema alone. It stops short of stating a preferred form or any validation behavior.

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 names the resource (a single Afefehub business) and the payload (summary plus every review), which is enough to distinguish it from search_businesses and top_businesses. The verb is only implied by the noun phrase 'Summary and every review of one business', so it falls just short of the crisp verb+resource form.

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: an agent can infer this is the lookup to call once it already has a specific business identifier. There is no explicit when-to-use or when-not-to-use framing, and no mention that discovery must happen via search_businesses or top_businesses first.

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