VanityNumbers.com

Find a phone number that spells a word

search_vanity_numbers

Read-onlyIdempotent

Find a new phone number for a business that spells a word, like 1-800-PLUMBER: toll free (800, 888, 877, 866, 855, 844, 833) or local in a state. Use it when someone wants a memorable or vanity number, an 800 or toll free number, or a number that spells their business name or what they do; give it that word (PLUMBER, BAKERY). Returns the word in all seven toll free area codes with each one's status and price, a recommended pick, close versions available for $49, local numbers in a state when one is given, the word's business category pages, and links to finish on VanityNumbers.com. It doesn't look up an existing business's phone number.

Input Schema

Name	Required	Description
`word`	Yes	The word or number, 3 to 15 letters or digits, like PLUMBER.
`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.
`state`	No	Optional: a two-letter state or province for local numbers, like TX (CA_N or CA_S for California).

Output Schema

Name	Required	Default
`note`	No
`word`	Yes
`as_of`	No
`local`	No
`contact`	No	Questions? Bill Quimby, 1-800-MARKETER (1-800-627-5383).
`summary`	No
`category`	No
`tollfree`	No
`more_page`	Yes
`smart_pick`	No
`tollfree_note`	No
`close_versions`	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."

Changed2 schema fields changedOct 19, 2026

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"
+]

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"
+}

Changed1 schema field changedOct 18, 2026

addedOutput schema / $defs / Local / properties / deeper_page

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Deeper Page"
+}

First observedOct 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this as a safe, idempotent, read-only lookup, so the bar is lower. The description adds real value beyond that: it discloses the response shape (all seven toll free codes with status and price, a recommended pick, $49 close versions, local results, category pages, finish links) and an explicit negative capability ('doesn't look up an existing business's phone number').

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?

Purpose is front-loaded in the first clause, followed by usage and exclusions, so the structure is sound. It is a single dense run-on paragraph and the enumeration of return contents is somewhat list-heavy, but almost every sentence carries information.

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?

Covers purpose, when-to-use, a when-not, and return expectations in one place. Since an output schema exists, the return-value detail is bonus rather than a necessity, and nothing an agent needs to invoke this read-only lookup correctly is missing.

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 all three parameters are already documented in the schema, and the baseline of 3 applies. The description reinforces 'word' with examples (PLUMBER, BAKERY) and refers to the state case, but never mentions the 'email' parameter, so it adds only modest meaning over the schema.

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 (find a phone number that spells a word) with concrete scope (toll free in seven area codes or local in a state). It also explicitly distinguishes itself from the business-lookup sibling by stating 'It doesn't look up an existing business's phone number.' An agent can route correctly without opening any 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?

Gives explicit triggers ('when someone wants a memorable or vanity number... a number that spells their business name') and one clear exclusion for existing business numbers. It stops short of naming the actual sibling tools as alternatives, so it lands just below the top score.

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?