Skip to main content
Glama

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

Agent Max: the hardest tasks

hubvibe_agent_task_max
Read-onlyIdempotent

HubVibe Agent (max): 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 20 steps. Charged only when the answer is delivered. Input: task; optional context, fields for a JSON answer, language. $20.00 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_max"
  }
}

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

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false), so the bar is lower, and the description still adds real operational context: a 20-step cap, delivery-contingent billing, and the $20.00 price. It also discloses the response shape (headline, key points, full answer, sources, every tool step). It does not state latency expectations or what happens if the step budget is exhausted without an answer.

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?

It is front-loaded with the one-call promise, then supported by a compact capability list, an explicit I/O summary, and pricing. The six-item example enumeration is slightly listy but each item is short and aids routing. Nothing is redundant enough to obstruct scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an expensive, open-ended agent with an output schema already published, the definition covers inputs, cost, step budget, and result shape adequately. The material gap is positioning among the three agent-tier siblings and failure/partial-result behavior, which matter for a $20 call. It does slightly restate return values that the output schema already provides.

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 the parameter burden. It names all four parameters and gives real meaning to two of them: `fields` produces "a JSON answer" and `language` controls output language, while `task` and `context` are only loosely characterized ("plain words," "optional context") with no mention of the 4000-char task limit, the 30-item field cap, or the language pattern.

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 states a concrete verb+outcome ("hand it any task in plain words and get the finished result in one call") and enumerates the domains it covers (research, website checks, name screening, markets, comparisons). It is clearly a general-purpose agent rather than a single-purpose API. It stops short of distinguishing itself from hubvibe_agent_task or hubvibe_agent_task_pro, leaving the "max" tier implied only by the title and the 20-step ceiling.

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?

Usage context is implied by "the max tier" framing, "Up to 20 steps," and the example task list, so an agent can infer this is for heavy multi-step work. However, there is no explicit "use this instead of hubvibe_agent_task/pro when..." routing statement, and no exclusions for tasks better served by the narrower siblings (e.g., hubvibe_contact_screen, hubvibe_company_enrich, hubvibe_finance_analytics).

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.