VanityNumbers.com

Find numbers for a type of business

find_business_numbers

Read-onlyIdempotent

Find toll free numbers for a type of business, like PLUMBING, DENTIST or LAWYER: the best ones available now (from 1800AVAILABLE.com) and recently disconnected ones that can be requested, up to 10 of each. Use it when someone wants to browse numbers for their kind of business rather than one word. Returns each number's price, and links to its page and to the category's page to see more.

Input Schema

Name	Required	Description	Default
`email`	No	Optional: the person's email, if they have a confirmed notification with VanityNumbers.com. The lookup is then connected to their notifications, so their emails' suggestions fit what they're looking for.
`business`	Yes	The kind of business, one word of 3 to 15 letters, like PLUMBING, DENTIST or LAWYER.

Output Schema

Name	Required	Default
`note`	No
`as_of`	No
`contact`	No	Questions? Bill Quimby, 1-800-MARKETER (1-800-627-5383).
`summary`	No
`business`	Yes
`category`	No
`available`	No
`more_page`	Yes
`disconnected`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedInput schema / properties / email / description

Previous value: -"Optional: the person's email, if they have a confirmed watch with VanityNumbers.com. The lookup is then connected to their watch, so its emails' suggestions fit what they're looking for."New value: +"Optional: the person's email, if they have a confirmed notification with VanityNumbers.com. The lookup is then connected to their notifications, so their emails' suggestions fit what they're looking for."

Changed1 schema field changedOct 19, 2026

addedOutput schema / properties / disconnected

Added value: +{
+  "default": [],
+  "items": {
+    "$ref": "#/$defs/BizNumber"
+  },
+  "title": "Disconnected",
+  "type": "array"
+}

Changed4 schema fields changedOct 19, 2026

removedOutput schema / $defs / BizNumber / properties / frees_up

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Frees Up"
-}

removedOutput schema / $defs / Category / properties / disconnects_page

Removed value: -{
-  "title": "Disconnects Page",
-  "type": "string"
-}

changedOutput schema / $defs / Category / required

Previous value: -[
-  "label",
-  "best_available_page",
-  "disconnects_page"
-]New value: +[
+  "label",
+  "best_available_page"
+]

removedOutput schema / properties / disconnected

Removed value: -{
-  "default": [],
-  "items": {
-    "$ref": "#/$defs/BizNumber"
-  },
-  "title": "Disconnected",
-  "type": "array"
-}

Changed1 schema field changedOct 18, 2026

addedInput schema / properties / email

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional: the person's email, if they have a confirmed watch with VanityNumbers.com. The lookup is then connected to their watch, so its emails' suggestions fit what they're looking for.",
+  "title": "Email"
+}

First observedOct 16, 2026

TDQS

A4.1/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, non-open-world behavior, so the bar is lower. The description still adds real context beyond them: the data source (1800AVAILABLE.com), two result cohorts (currently available 'best' vs. recently disconnected and requestable), and a hard cap of 'up to 10 of each.'

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 verb+resource before the usage condition, and each clause carries information (examples, cap, return contents). Slightly long and appositive-heavy, but no wasted sentences.

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?

An output schema exists, so return-value explanation isn't required, yet the description helpfully notes price and page/category links. Scope, trigger, result cohorts, and limits are covered; only edge behavior (e.g., no results for a category, use of the email context) is 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 description coverage is 100%, so both parameters are already documented and the baseline is 3. The description restates the business examples already present in the schema and says nothing about the optional email parameter's effect, so it adds no meaning beyond the structured fields.

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?

Specific verb+resource: 'Find toll free numbers for a type of business,' with concrete examples (PLUMBING, DENTIST, LAWYER). It also implicitly distinguishes itself from sibling search_vanity_numbers by scoping to a business category 'rather than one word,' so an agent can route correctly 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 Guidelines4/5

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

States an explicit trigger: 'Use it when someone wants to browse numbers for their kind of business rather than one word.' That contrast effectively selects this tool over single-word searching, though no sibling is named by title and no exclusion for the other four tools is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All VanityNumbers.com tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?