Skip to main content
Glama

Google Business Profile & Local SEO Checker

Check business name for suspension risk

check_business_name
Read-onlyIdempotent

Checks a Google Business Profile name against Google's naming rules (no keywords, locations, taglines, phone numbers, hours). Keyword-stuffed names are the most common cause of suspensions. Returns PASS/RISK/FAIL, each problem with its fix, and the likely real name.

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

Input Schema

NameRequiredDescriptionDefault
cityNoOptional: city or suburb the business is in
nameYesThe name exactly as it appears on the profile
categoryNoOptional: primary GBP category
legal_or_signage_nameNoOptional: the name on signage, invoices or ABN registration. Words also in this name are allowed

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 cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the output contract: PASS/RISK/FAIL verdicts, per-problem fixes, and a suggested real name. That is genuinely useful behavioral detail given no output schema exists, though nothing is said about edge cases such as ambiguous names or empty results.

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?

Three tight sentences: what it does, why it matters, and what comes back. The verdict-format information is placed last and the rule list is front-loaded, with no filler.

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?

With no output schema, the description correctly compensates by summarizing the return shape and per-problem fixes. Combined with fully documented parameters and rich annotations, an agent has enough to call it correctly, with only edge-case behavior left unstated.

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%, so all four parameters, including the allowance that words in legal_or_signage_name are permitted, are already documented in the schema. The description adds no further guidance on how city or category influence the verdict, so the 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?

States a specific verb and resource ('Checks a Google Business Profile name') and enumerates exactly what is being checked against ('no keywords, locations, taglines, phone numbers, hours'). This clearly separates it from sibling checks like check_gbp_description or check_gbp_post, which inspect different profile assets.

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?

Gives clear context for when it matters ('Keyword-stuffed names are the most common cause of suspensions'), framing it as a pre-emptive risk check. It names no explicit alternatives or exclusions (e.g. no pointer to suspension_triage for already-suspended profiles), so it stops short of full routing guidance.

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