Skip to main content
Glama

Check a business fact (phone, hours, address)

field_check
Read-onlyIdempotent

Call before using a phone number, address, opening hours or service area you hold for a business. One signed verdict per business field. field=phone|address|hours|service_area and value= the value you hold. phone: matches, former_value (with dates), not_this_business (the site never published it and another publisher is named with the page that prints it), or not_published. address: matches, same_street_other_city, former_value, not_this_business, not_published or nothing_declared. hours: a week (Mo-Fr 08:00-17:00) gives matches or differs per day; a moment (Sa 10:00) gives open or closed. service_area: declared, not_declared or nothing_declared. Built from the business's own site (and its Business Profile for the licence holder), its dated fact history, CrawlCheck's scans of other sites, and for an unknown number a web search whose cited pages are read plus a YellowPages reverse lookup.

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": {
      "domain": "<domain>",
      "field": "<field>",
      "value": "<value>"
    },
    "name": "field_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYes
valueYesThe value you hold: a 10-digit number, a street address, a week (Mo-Fr 08:00-17:00) or a moment (Sa 10:00), or a place name
domainYesBare domain of the business, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the description's job is to add context — and it does: it discloses the evidence base (the business's own site, its Business Profile, dated fact history, CrawlCheck scans of other sites, web search plus YellowPages reverse lookup for unknown numbers). It does not mention latency, cost, or failure behavior for open-world lookups, which keeps it from 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.

Conciseness4/5

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

Front-loaded with the action and the precondition, then the verdict vocabulary, then provenance — a sensible order with no filler sentences. The final sentence is a long run-on with nested parentheticals, which costs some readability, but every clause carries substantive information.

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?

No output schema exists, so the description correctly spends its space enumerating the verdict tokens per field, which is exactly what an agent needs to interpret results. The remaining gap is the unexplained term 'signed verdict' (what is signed, and how a signature should be read), which leaves a small hole for a three-parameter tool with open-world lookups.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 67% schema coverage, the description meaningfully extends the schema: it enumerates field values and maps each to its value form (10-digit number, street address, a week like 'Mo-Fr 08:00-17:00' versus a moment like 'Sa 10:00', or a place name). It also explains that the value's form changes the verdict set for hours, which is semantics the schema does not carry.

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 (check) plus the exact resource class (a business fact: phone, address, hours, service area) and the triggering situation ('before using a phone number, address, opening hours or service area you hold'). That is clearly separable from siblings like check_site_safety or video_check.

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 opening sentence gives an explicit when-to-use rule: call this before relying on a business fact you already hold. It also implies one field per call ('One signed verdict per business field'). It stops short of naming when NOT to use it or which sibling to prefer for adjacent needs.

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.