Skip to main content
Glama

Google Business Profile & Local SEO Checker

Settle a business name against the website

verify_business_name
Read-onlyIdempotent

Checks a Google Business Profile name against Google's naming rules, then reads the business's own website to decide whether the flagged words are the genuine real-world brand (allowed) or were added to the listing for ranking (not allowed). Reads the site's title, schema.org markup, og:site_name, logo alt text, footer and ABN. Use this instead of check_business_name whenever a website is available.

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

Input Schema

NameRequiredDescriptionDefault
cityNoOptional: city or suburb
nameYesThe name exactly as it appears on the Google profile
websiteNoThe business's website. Without it this falls back to the plain rule check
categoryNoOptional: primary GBP category
legal_or_signage_nameNoOptional: the name on signage, invoices or ABN registration

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the evidence sources it inspects (title, schema.org, og:site_name, logo alt text, footer, ABN) and the decision criterion (genuine brand vs. added for ranking). It does not discuss latency, rate limits, or what a partial/ambiguous verdict looks like, which keeps it short of a 5.

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 core action and the decision logic, then the evidence list, then the sibling routing. No filler and no repetition of the title.

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 carries the burden of indicating the result, and it does so by framing the outcome as allowed vs. not allowed. For a five-parameter read-only verification tool this is nearly complete, though it could say more about what happens when the website is unreachable or the evidence is inconclusive.

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%, so every parameter is already documented, and the description largely restates the website fallback that the schema already states. It adds only marginal meaning, such as implying legal_or_signage_name feeds the ABN check, so the baseline of 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 against Google's naming rules') and then describes the second stage of reading the business's own website. It explicitly names the sibling it replaces, so an agent can distinguish it from check_business_name without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: 'Use this instead of check_business_name whenever a website is available,' and the schema note clarifies the fallback when no website is supplied. Both the when-to-use and the when-not-to-use condition are stated.

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.