Skip to main content
Glama

ReviewTactic — Google Review Checker

Find a business on Google Maps

find_business
Read-only

Looks up a local business by name and town and returns up to 5 matching Google Maps listings with place_id, address, rating, review count, coordinates and a link for writing a review. Use it to get the place_id or coordinates that the other tools need.

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

Input Schema

NameRequiredDescriptionDefault
queryYesBusiness name and town or address, e.g. "Joe's Pizza Brooklyn".

Output Schema

NameRequiredDescriptionDefault
statusYes
messageNo
candidatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and openWorld behavior, so the description's added value is the result cap ('up to 5 matching listings') and the downstream-dependency role. It does not say how ambiguity between multiple matches is resolved or what an empty result looks like, which would matter for an open-world lookup.

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?

Two sentences, front-loaded with the lookup scope and followed by the dependency hint; nothing is padding. The enumeration of return fields is slightly redundant against the output schema but stays brief.

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?

For a single-parameter read-only lookup with full schema coverage, annotations and an output schema, the description covers purpose, result limit and role in the workflow. Nothing needed to invoke it correctly is missing.

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 coverage is 100% and the query parameter already carries a concrete 'name + town' example. The description's 'by name and town' reinforces the intended composition but adds no syntax, formatting, or edge-case meaning beyond the schema.

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 ('Looks up a local business by name and town') and enumerates the return payload (place_id, address, rating, review count, coordinates, review link). It also positions itself relative to the other tools by noting it supplies the place_id/coordinates they need, though it never names a specific sibling.

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 to get the place_id or coordinates that the other tools need' gives a clear when-to-use rule as a prerequisite lookup step. There is no when-not-to-use guidance or explicit statement of what to do when zero or multiple businesses match.

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.