HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News

Phone number intelligence: valid, where, which network, what type

hubvibe_phone_parse

Read-onlyIdempotent

Phone number validation and lookup: valid or not, country and area, the carrier the range was issued to, line type (mobile, landline, toll-free, VoIP, premium), time zones and E.164, international and national formats, from Google's libphonenumber numbering plans. Nothing is dialled and the owner is never looked up. Input: number; optional region for a national-format number. $0.02 per call. Returns: input{}, valid, possible, e164, international, national, country_code, region, country, location, carrier, line_type, time_zones[], metadata_version, notes[], checked_at.

Input Schema

TableJSON Schema

Name	Required	Description
`number`	Yes	One phone number, international (+44 20 7946 0958) or national with `region`.
`region`	No	Two-letter country code for a national-format number (GB, US).
`language`	No	Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable strings of the result (notes, details, reasons) are translated into this language; data, codes, numbers and URLs are untouched. Default: as produced.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes
`status`	Yes
`worker`	Yes
`price_usd`	Yes
`provenance`	Yes
`receipt_id`	Yes
`attribution`	No
`receipt_url`	Yes
`billing_warning`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedOct 1, 2026

removedOutput schema / description

Removed value: -"The 200 body of every paid /work call. `result` is the worker's own output (its schema is per route); everything else is the same on every /work route. A receipt for the job is at `receipt_url`."

removedOutput schema / properties / attribution / description

Removed value: -"Present only when the result's text was machine-translated: the credit to show with it."

removedOutput schema / properties / attribution / items / description
```
Removed value: -"A credit."
```

removedOutput schema / properties / attribution / items / properties

Removed value: -{
-  "text": {
-    "description": "Credit.",
-    "examples": [
-      "Translated by Google"
-    ],
-    "type": "string"
-  },
-  "url": {
-    "description": "Link.",
-    "examples": [
-      "https://translate.google.com"
-    ],
-    "type": "string"
-  }
-}

removedOutput schema / properties / attribution / items / required
```
Removed value: -[
-  "text",
-  "url"
-]
```
removedOutput schema / properties / attribution / items / type
```
Removed value: -"object"
```

removedOutput schema / properties / billing_warning / description

Removed value: -"Present only when the charge was recorded with a caveat."

removedOutput schema / properties / billing_warning / examples
```
Removed value: -[
-  "settlement pending"
-]
```
removedOutput schema / properties / price_usd / description
```
Removed value: -"What this call cost, in USD."
```
removedOutput schema / properties / price_usd / examples
```
Removed value: -[
-  0.02
-]
```

removedOutput schema / properties / provenance / description

Removed value: -"How the result was produced: which providers ran and how long each took."

removedOutput schema / properties / provenance / properties

Removed value: -{
-  "attempts": {
-    "description": "Provider attempts made, including retries and failovers.",
-    "examples": [
-      1
-    ],
-    "type": "integer"
-  },
-  "elapsed_ms": {
-    "description": "Wall-clock milliseconds for the whole job.",
-    "examples": [
-      340
-    ],
-    "type": "integer"
-  },
-  "providers_used": {
-    "description": "Providers that served the job.",
-    "examples": [
-      [
-        "coinbase-advanced-trade-public"
-      ]
-    ],
-    "items": {
-      "description": "Provider name.",
-      "examples": [
-        "coinbase-advanced-trade-public"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "steps": {
-    "description": "Every step the job ran, in order.",
-    "items": {
-      "description": "One step of the job.",
-      "properties": {
-        "ms": {
-          "description": "Milliseconds the step took.",
-          "examples": [
-            312
-          ],
-          "type": "integer"
-        },
-        "ok": {
-          "description": "Whether the step succeeded.",
-          "examples": [
-            true
-          ],
-          "type": "boolean"
-        },
-        "provider": {
-          "description": "Provider that served the step.",
-          "examples": [
-            "coinbase-advanced-trade-public"
-          ],
-          "type": "string"
-        },
-        "reason": {
-          "description": "Failure reason, on a failed step.",
-          "examples": [
-            "provider_timeout"
-          ],
-          "type": "string"
-        },
-        "step": {
-          "description": "Step name inside the worker.",
-          "examples": [
-            "quote"
-          ],
-          "type": "string"
-        }
-      },
-      "required": [
-        "step",
-        "ok",
-        "ms"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  }
-}

removedOutput schema / properties / provenance / required

Removed value: -[
-  "steps",
-  "providers_used",
-  "attempts",
-  "elapsed_ms"
-]

removedOutput schema / properties / receipt_id / description
```
Removed value: -"Receipt id for this job."
```
removedOutput schema / properties / receipt_id / examples
```
Removed value: -[
-  "rcpt_9f1c2b3a4d5e6f70"
-]
```

removedOutput schema / properties / receipt_url / description

Removed value: -"Where to fetch the machine-readable receipt (free, no payment)."

removedOutput schema / properties / receipt_url / examples

Removed value: -[
-  "/work/receipts/rcpt_9f1c2b3a4d5e6f70"
-]

removedOutput schema / properties / result / properties

Removed value: -{
-  "carrier": {
-    "description": "Network the number range was issued to; null when not recorded (common for fixed lines).",
-    "examples": [
-      "T-Mobile"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "checked_at": {
-    "description": "When this node read the source (UTC). Nothing here is cached.",
-    "examples": [
-      "2026-09-26T18:00:00Z"
-    ],
-    "format": "date-time",
-    "type": "string"
-  },
-  "country": {
-    "description": "Country name.",
-    "examples": [
-      "United Kingdom"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "country_code": {
-    "description": "Calling code.",
-    "examples": [
-      44
-    ],
-    "type": "integer"
-  },
-  "e164": {
-    "description": "E.164 form.",
-    "examples": [
-      "+442070313000"
-    ],
-    "type": "string"
-  },
-  "input": {
-    "description": "The request.",
-    "properties": {
-      "number": {
-        "description": "The number as given.",
-        "examples": [
-          "+44 20 7031 3000"
-        ],
-        "type": "string"
-      },
-      "region": {
-        "description": "Region used for a national number.",
-        "examples": [
-          "GB"
-        ],
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "number",
-      "region"
-    ],
-    "type": "object"
-  },
-  "international": {
-    "description": "International format.",
-    "examples": [
-      "+44 20 7031 3000"
-    ],
-    "type": "string"
-  },
-  "line_type": {
-    "description": "Kind of line.",
-    "enum": [
-      "fixed_line",
-      "mobile",
-      "fixed_line_or_mobile",
-      "toll_free",
-      "premium_rate",
-      "shared_cost",
-      "voip",
-      "personal_number",
-      "pager",
-      "uan",
-      "voicemail",
-      "unknown"
-    ],
-    "examples": [
-      "fixed_line"
-    ],
-    "type": "string"
-  },
-  "location": {
-    "description": "Area the number was issued to (city or region); null when unknown.",
-    "examples": [
-      "London"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "metadata_version": {
-    "description": "libphonenumber metadata version used.",
-    "examples": [
-      "9.0.40"
-    ],
-    "type": "string"
-  },
-  "national": {
-    "description": "National format.",
-    "examples": [
-      "020 7031 3000"
-    ],
-    "type": "string"
-  },
-  "notes": {
-    "description": "Caveats.",
-    "examples": [
-      []
-    ],
-    "items": {
-      "description": "A caveat.",
-      "examples": [
-        "Answered from the number alone."
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "possible": {
-    "description": "The length is possible for the country.",
-    "examples": [
-      true
-    ],
-    "type": "boolean"
-  },
-  "region": {
-    "description": "ISO country code the number belongs to.",
-    "examples": [
-      "GB"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "time_zones": {
-    "description": "Time zones the number's area uses.",
-    "examples": [
-      [
-        "Europe/London"
-      ]
-    ],
-    "items": {
-      "description": "An IANA time zone.",
-      "examples": [
-        "Europe/London"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "valid": {
-    "description": "A valid number in its country's numbering plan.",
-    "examples": [
-      true
-    ],
-    "type": "boolean"
-  }
-}

removedOutput schema / properties / result / required

Removed value: -[
-  "input",
-  "valid",
-  "possible",
-  "e164",
-  "international",
-  "national",
-  "country_code",
-  "region",
-  "country",
-  "location",
-  "carrier",
-  "line_type",
-  "time_zones",
-  "metadata_version",
-  "notes",
-  "checked_at"
-]

removedOutput schema / properties / status / description

Removed value: -"Present only on a delivered result."

removedOutput schema / properties / worker / description

Removed value: -"Catalog name of the worker that ran."

removedOutput schema / properties / worker / examples
```
Removed value: -[
-  "market.quote"
-]
```
removedOutput schema / title
```
Removed value: -"phone.parse response"
```

AddedSep 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuine context beyond that: the underlying data source (Google libphonenumber numbering plans), explicit no-side-effect guarantees, and a per-call price ($0.02), which is real behavioral disclosure. It loses a point only because the enumerated return list duplicates the 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?

Front-loads the purpose and capabilities efficiently, and the no-dial/no-owner clause comes early. The trailing 'Returns: input{}, valid, possible, e164...' enumeration is largely redundant given an output schema exists, making the tail slightly wasteful.

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?

For a single-number lookup with full schema coverage and a defined output schema, nothing an agent needs is missing: capability, input contract, side-effect profile, data source, and cost are all present.

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 coverage is 100%, so all three parameters — including `language`, which the description never mentions — are already documented. The description restates the number/region contract but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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+resource (validation and lookup of a phone number) and enumerates the exact facets it returns: validity, country/area, carrier, line type, time zones, formats. No sibling tool in the list does phone parsing, so it is unambiguous.

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?

It frames the usage context (pass a number; region only needed for national-format input) and adds negative scope — 'Nothing is dialled and the owner is never looked up' — which steers the agent away from treating it as an identity/enrichment tool. No explicit alternatives are named, but none exist among the siblings.

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

All HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News 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.