Skip to main content
Glama

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

Agent: get a task done

hubvibe_agent_task
Read-onlyIdempotent

HubVibe Agent (quick): hand it any task in plain words and get the finished result in one call. Research a company or a person of interest, check a website, screen a name, read the markets, compare options, pull the facts: you get a headline, the key points, the full answer, its sources and every tool step. Up to 4 steps. Charged only when the answer is delivered. Input: task; optional context, fields for a JSON answer, language. $2.75 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": {
      "task": "<task>"
    },
    "name": "hubvibe_agent_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes
fieldsNo
contextNo
languageNo

Output Schema

NameRequiredDescriptionDefault
resultYes
statusYes
workerYes
price_usdYes
receipt_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • removedInput schema / properties / context / description
      Removed value: -"Optional material the task refers to (text or JSON)."
    • removedInput schema / properties / fields / description
      Removed value: -"Optional: also return `data` with exactly these keys."
    • removedInput schema / properties / language / description
      Removed value: -"Optional answer language, BCP-47 (en, ja, pt-BR). Default: the input's."
    • removedInput schema / properties / task / description
      Removed value: -"The task, in plain words."
    • 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/5.0
Behavior5/5

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

Beyond the annotations (read-only, open-world, idempotent, non-destructive), the description discloses the operational envelope an agent actually needs: a 4-step ceiling, billing contingent on delivery, and a $2.75 per-call price. That pricing and step-limit information cannot be recovered from the annotations or schema and directly affects whether an agent should call this tool.

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 first sentence front-loads the core promise, and each subsequent clause adds something (output shape, step cap, billing, inputs, price). The mid-sentence list of example tasks is slightly rambling but earns its place by illustrating scope; no clause is pure filler.

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?

For an open-world agent tool with an output schema already present, the definition covers what is needed: inputs, step cap, output shape, and cost model including the no-delivery no-charge rule. The remaining gap is comparative positioning against the pro/max variants rather than missing call-critical detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does name all four parameters with intent: task, optional context, fields for a JSON answer, and language. It falls short of explaining accepted shapes (context allows string/object/array) or the 4000-char task limit, so meaning is added but not completely.

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?

"HubVibe Agent (quick): hand it any task in plain words and get the finished result in one call" gives a concrete agent-orchestration action with a clear input/output contract. The "(quick)" label plus "Up to 4 steps" partially differentiates it from hubvibe_agent_task_pro/max, but the description never names those siblings, so the boundary is inferred rather than stated.

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?

The description supplies rich usage context through example tasks (research a company, screen a name, read markets), which tells an agent what kinds of requests fit. However, it offers no exclusions and no routing advice toward the deeper pro/max variants; the 4-step cap only implicitly signals that longer multi-step work belongs elsewhere.

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.