Skip to main content
Glama

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

Website opportunity assessment for a supplied URL

hubvibe_lead_qualify
Read-onlyIdempotent

Assess an existing business website supplied by the caller (not lead discovery). One plain HTTP fetch (no browser) produces SEO and security-header findings, static accessibility signals, platform and marketing tags, domain mail setup (MX, SPF, DMARC), company profile, and a 0-100 website opportunity score with suggested outreach hooks. Input: url; optional business_name. Does not find prospects, contact details, or verify buying intent. $0.25 per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "hubvibe_lead_qualify"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
languageNo
business_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes
statusYes
workerYes
price_usdYes
receipt_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedInput schema / properties / business_name / description
      Removed value: -"The business's name, to help the company lookup. Optional."
    • 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 / url / description
      Removed value: -"The business's website, http(s)."
    • 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. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety bar is met structurally; the description still adds real value by disclosing the execution model ('one plain HTTP fetch, no browser'), which explains why JavaScript-rendered signals may be missing. The explicit '$0.25 per call' cost disclosure is behaviorally important and is not derivable from annotations.

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?

Two dense sentences that front-load the verb, the scope, and the exclusion before listing outputs and price. The output enumeration is somewhat long, but every clause names a distinct deliverable rather than padding; no filler or hedging.

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 the description did not need to enumerate return values, and its doing so is a bonus rather than a requirement. The one real gap is the undocumented language parameter, which is the only thing an agent could get wrong; execution model, cost, and exclusions are all covered.

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%, so the description must carry parameter meaning, and it only partly does: it states 'Input: url; optional business_name', matching the schema's single required field, but gives no URL format expectations and never mentions the third parameter, language. Two of three parameters get a bare mention and one gets nothing, so it adds marginal meaning beyond the schema's type and required list.

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 plus resource: 'Assess an existing business website supplied by the caller', with an immediate parenthetical scoping it away from lead discovery. It also enumerates the concrete outputs (SEO, security headers, accessibility signals, mail setup, opportunity score), so an agent can distinguish it from siblings like hubvibe_extract_page or hubvibe_company_enrich 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?

Explicit when-not guidance is present: 'not lead discovery', 'Does not find prospects, contact details, or verify buying intent', which prevents the most likely misuse. It stops short of naming a concrete alternative sibling to use for those excluded cases, so it is clear context with exclusions rather than full routing.

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.