Skip to main content
Glama

Check a pest control phone number

verify_phone
Read-onlyIdempotent

Check a pest control company's phone number against official state license records. Give it the number on the van, the flyer, the voicemail or the caller ID and it returns the license records that publish that exact number, each with the business name, license number, issuing state, the official state source link and the date PestPin last processed that source. Use it when someone has a number and wants to see which license records publish it, before they hire or let anyone in. The state lookups PestPin works with are searched by business name or license number, so a number on its own is normally a dead end; this covers 35 states. The match is exact on ten digits and never partial, so a number one digit different is a different company and is never offered. A match means a license record publishes that number: it does not say who answered, whether the caller works for that company, or anything about insurance or work quality. No match is not proof anyone is unlicensed: coverage is 35 states, about half of all listings publish no phone at all, and a licensed company can publish a number PestPin does not hold. Records from states that license the individual operator rather than a firm are never returned here, because a phone number is not a way to look up a private person; they are counted in withheld and the license-number lookup returns them. It looks up a business's published number, never a person's own.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
businessPhoneYesThe pest control company's published phone number, e.g. 713-555-0100. Dashes, brackets, spaces, a leading 1 and an extension are all accepted. A business's number, not the person's own.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYesThe limits a reader must be told
matchesYesLicense records publishing that number, empty when none does
withheldNoMatching records deliberately left out because that state licenses the individual operator rather than a firm. Zero when nothing was withheld.
phoneNumberNoThe ten digits the number was read as
totalMatchesYesHow many records publish that number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / businessPhone / description
      Previous value: -"The pest control company's published phone number, e.g. 713-555-0100. Dashes, brackets, spaces, a leading 1 and an extension are all accepted. Never the person's own number."New value: +"The pest control company's published phone number, e.g. 713-555-0100. Dashes, brackets, spaces, a leading 1 and an extension are all accepted. A business's number, not the person's own."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

The description goes far beyond the annotations by disclosing exact ten-digit matching, what a match does and does not imply, open-world limitations, 35-state coverage, and the exclusion of individual-operator records. These details align with openWorldHint and readOnlyHint without contradicting them.

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?

The description is front-loaded with purpose and output, then covers use cases and caveats. It is longer than strictly necessary, with some repetition around the business-vs-person distinction, but every sentence contributes operational meaning for a tool with subtle matching semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given one parameter, full schema coverage, and an output schema, the description covers input sources, return contents, exact-match behavior, no-match interpretation, state coverage, and alternative lookups. Nothing an agent needs to invoke it correctly is missing.

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?

The schema already documents the single parameter with examples and accepted formats, so the baseline is 3. The description adds real-world input sources ('the number on the van, the flyer, the voicemail or the caller ID') and reinforces that it must be a business number, not a personal one, which helps an agent map user intent to the parameter.

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?

The description opens with a specific verb and resource: 'Check a pest control company's phone number against official state license records.' It also lists the exact output fields, which distinguishes it from sibling tools like verify_license that operate on license numbers rather than phone numbers.

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?

It explicitly states when to use the tool: 'Use it when someone has a number and wants to see which license records publish it, before they hire or let anyone in.' It also gives exclusions, such as never looking up a person's own number, and points to the license-number lookup as the alternative for individual-operator records.

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