Skip to main content
Glama

Google Business Profile & Local SEO Checker

Compare name, address, phone across listings

compare_nap
Read-onlyIdempotent

Checks that a business's name, address and phone (NAP) match across directory listings, ignoring formatting differences (St vs Street, +61 vs 0, Pty Ltd). Paste each listing's details or text. Returns real mismatches and a list of Australian directories worth having.

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": {
      "reference": "<reference>",
      "listings": "<listings>"
    },
    "name": "compare_nap"
  }
}

Input Schema

NameRequiredDescriptionDefault
listingsYesListings to compare
referenceYesThe correct details, as on the Google profile

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 value beyond that: the normalization rules applied before comparison, and the fact that it returns only "real mismatches" plus an Australian directory list — useful since 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences: what it does, how to feed it, what comes back. The trailing directory-list clause is slightly incidental but earns its place as return-value disclosure given no output schema.

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 read-only comparison tool with nested objects and no output schema, the description covers purpose, input mode, normalization behavior and return contents. Minor gaps remain: it doesn't say how mismatches are represented or what happens with an empty listings array.

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 the properties (reference, listings, source, text) are already documented, including the fields-or-paste-text alternative. The description adds only the normalization examples (St vs Street, +61 vs 0, Pty Ltd), which clarify intent but not parameter usage beyond the schema baseline.

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 — checks that name, address and phone match across directory listings — with a clear comparison scope. It implicitly separates itself from single-field siblings like check_business_name by comparing reference against multiple listings, but never names an alternative explicitly.

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

Usage Guidelines3/5

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

"Paste each listing's details or text" tells the agent how to supply input, which is genuine usage guidance. However, there is no when-to-use vs when-not guidance and no routing to siblings such as check_business_name or audit_gbp_profile if the agent is unsure which check applies.

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.