Skip to main content
Glama

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

Contact and sanctions screening (not identity verification)

hubvibe_contact_screen
Read-onlyIdempotent

Screen a name against sanctions lists, evaluate email deliverability and disposable signals, validate a phone number's numbering plan and inspect IP geography/network. Returns findings, per-check completion, and a screening risk indicator. Never proves document authenticity, ownership or liveness, and is NOT complete KYC or identity verification. Inconclusive/failed checks cannot produce a low-risk result. Input: any of name, email, phone, ip; optional country/birth_year. $0.10 per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hubvibe_contact_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNo
nameNo
emailNo
phoneNo
countryNo
languageNo
birth_yearNo
phone_regionNo

Output Schema

NameRequiredDescriptionDefault
resultYes
statusYes
workerYes
price_usdYes
receipt_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • removedInput schema / properties / birth_year / description
      Removed value: -"Birth year, to narrow sanctions matches for a person."
    • removedInput schema / properties / country / description
      Removed value: -"Country the person says they are in (US or United States), compared with phone and IP."
    • removedInput schema / properties / email / description
      Removed value: -"Email address to verify."
    • removedInput schema / properties / ip / description
      Removed value: -"The client's IPv4 or IPv6 address."
    • removedInput schema / properties / language / description
      Removed value: -"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."
    • removedInput schema / properties / name / description
      Removed value: -"Person or company name to screen against sanctions lists."
    • removedInput schema / properties / phone / description
      Removed value: -"Phone number, international (+44 20 7946 0958) or national with `phone_region`."
    • removedInput schema / properties / phone_region / description
      Removed value: -"Two-letter country for a national-format phone number."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / properties / attribution
      Removed value: -{
      -  "items": {},
      -  "type": "array"
      -}
    • removedOutput schema / properties / billing_warning
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / provenance
      Removed value: -{
      -  "type": "object"
      -}
    • removedOutput schema / properties / receipt_id
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / status / type
      Removed value: -"string"
    • changedOutput schema / required
      Previous value: -[
      -  "status",
      -  "worker",
      -  "price_usd",
      -  "result",
      -  "provenance",
      -  "receipt_id",
      -  "receipt_url"
      -]New value: +[
      +  "status",
      +  "worker",
      +  "price_usd",
      +  "result",
      +  "receipt_url"
      +]
  2. Changed2 schema fields changed
    • removedInput schema / anyOf
      Removed value: -[
      -  {
      -    "required": [
      -      "name"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "email"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "phone"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "ip"
      -    ]
      -  }
      -]
    • addedInput schema / minProperties
      Added value: +1
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's job is to add beyond that, and it does: it discloses the return composition (findings, per-check completion, risk indicator), a non-obvious failure semantic ('inconclusive/failed checks cannot produce a low-risk result'), and the cost ('$0.10 per call'). It does not discuss rate limits or partial-input behavior, but the added behavioral context is well above the annotation baseline.

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 definition is dense but well front-loaded: capability first, then return shape, then exclusions, then inputs and price. The opening sentence is a long run-on stacking four checks, and the input/price line reads like a compact trailer rather than prose, but no sentence is filler.

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 an output schema exists, the description does not need to detail return fields, yet it still summarizes them. Combined with explicit scope exclusions, the at-least-one-input constraint, optional demographic inputs and per-call pricing, an agent has enough to decide and invoke correctly. The only residual gap is per-parameter format detail, which is a schema-level issue rather than a description omission.

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 0% across 8 parameters, so the description must carry the burden and it only partly does. It names name, email, phone, ip, country and birth_year and marks the latter two optional, implying at least one input is required (matching minProperties=1), but it omits 'language' and 'phone_region' entirely and gives no format expectations (ISO country, E.164 phone, IPv4/IPv6).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names four concrete checks (sanctions screening, email deliverability/disposable signals, phone numbering plan, IP geography/network) with specific verbs, so an agent knows exactly what work happens. It also distinguishes itself from identity verification/KYC in both the title and body. It stops short of naming sibling tools like hubvibe_sanctions_screen or hubvibe_email_verify as the narrower alternatives, so sibling routing is only implied.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

There is clear negative guidance ('NOT complete KYC or identity verification', 'never proves document authenticity, ownership or liveness') which tells the agent when this tool is insufficient. Input guidance ('any of name, email, phone, ip') implies the composite nature. However, it never states when to prefer this combined screen over the single-purpose siblings such as hubvibe_sanctions_screen or hubvibe_email_verify, leaving that choice to inference.

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.