Skip to main content
Glama

Google Business Profile & Local SEO Checker

Check a review request message

check_review_request
Read-onlyIdempotent

Checks the SMS or email a business sends to ask for Google reviews against Google's review policy and the Australian Consumer Law: incentives, review gating (only asking happy customers), asking for 5 stars, scripting the review. Returns problems, fixes and a compliant template.

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": {
      "message": "<message>"
    },
    "name": "check_review_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe review request message text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 real substance beyond that: the four concrete compliance dimensions examined (incentives, review gating, 5-star asks, scripting) and the three-part shape of the output (problems, fixes, compliant template), which is valuable given there is no output schema.

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?

A single front-loaded sentence with zero filler: scope first, then the standards applied, then the checked categories via a compact colon list, then the return shape. Every clause carries information an agent needs.

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, no-output-schema tool, the description is nearly self-sufficient: input scope, applied rules, and output contents are all stated. Minor gaps remain, such as whether findings carry severity or ordering and whether the Australian Consumer Law scope implies jurisdiction limits on the advice.

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?

With a single parameter and 100% schema description coverage, the schema already fully documents 'message'. The description only adds that the message is one a business sends to solicit Google reviews, which is marginal added meaning over the schema's own 'review request message text' label. Baseline 3 applies.

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?

Names a specific verb (checks) and a precisely scoped resource (the SMS or email a business sends asking for Google reviews) against two named standards, Google's review policy and the Australian Consumer Law. This is clearly distinct from sibling checks such as check_review_reply, which targets replies rather than request messages.

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?

The object being audited is defined tightly enough that an agent knows exactly what input qualifies, and the enumerated violation types signal the intended use case. It stops short of explicitly naming alternatives or stating when not to use it (e.g. for replies or for other jurisdictions' rules), leaving that 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