Skip to main content
Glama

Google Business Profile & Local SEO Checker

Benchmark against real Australian businesses

benchmark_business
Read-onlyIdempotent

Where a business actually sits against real Australian Google Business Profiles in the same Google primary category: review-count and star-rating percentiles, the gap to the median and the top quartile in reviews and in months, and how common a rule-breaking name is in that category. Built from Kangaroo Growth's own Google Maps scrape, not from a survey. Use it any time someone asks whether their reviews or rating are good.

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": "benchmark_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
tradeNoOr plain English, e.g. electrician, carpet cleaner. Used if category is missing or unknown
ratingNoCurrent Google star rating, e.g. 4.6
categoryNoGoogle primary category, e.g. Electrician, Beauty salon
review_countNoCurrent Google review count
business_nameNoOptional, for labelling

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 bar is met; the description adds genuine value beyond them by disclosing data provenance (Kangaroo Growth's own Google Maps scrape, not a survey) and geographic scope (Australian businesses only). The provenance statement is exactly the kind of trust/scope context an agent needs when presenting numbers to a user.

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?

The opening clause front-loads the core operation, the middle enumerates outputs compactly, and the closing sentence tells the agent exactly when to reach for it. No filler or repeated annotation metadata.

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

Completeness5/5

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

There is no output schema, and the description compensates by listing the return dimensions (percentiles, gaps, rule-breaking name prevalence) explicitly. Combined with the provenance and scope notes, an agent has everything needed to call it and to explain the results.

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% and every parameter carries its own description (including the 'used if category is missing or unknown' fallback for trade), so the schema already does the heavy lifting. The description adds the concept of a 'Google primary category' as the matching key but gives no new guidance on rating format, review_count units, or what happens when category and trade conflict.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific analytical operation (positioning a business against real Australian Google Business Profiles in the same primary category) and enumerates the concrete outputs: review-count and star-rating percentiles, gap to median and top quartile in reviews and months, and rule-breaking name frequency. That is far more than a restatement of the name 'benchmark_business' and lets an agent distinguish it from audit/check siblings without opening the schema.

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?

"Use it any time someone asks whether their reviews or rating are good" gives a clear triggering condition tied to a real user question. It stops short of explicitly excluding adjacent cases (e.g. when the agent should run audit_business or check_business_name first) or naming an alternative, so it is clear context without exclusions.

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.