Skip to main content
Glama

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

Agent Pro: a deeper task

hubvibe_agent_task_pro
Read-onlyIdempotent

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

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.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/no-destructive, so the safety profile is covered; the description adds the genuinely non-obvious facts an agent needs: a hard 10-step ceiling, billing semantics ('charged only when the answer is delivered'), a flat $9.00 per call, and the shape of the delivered result (headline, key points, full answer, sources, tool steps). It stops short of describing failure/refund behavior when no answer is delivered or latency characteristics, so it lands at 4 rather than 5.

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-loaded with the core promise ('get the finished result in one call'), then constraints (10 steps, pricing), then inputs — a sensible order with no filler sentences. The mid-sentence example list is long but each item clarifies scope; the closing 'Input: ...' fragment is terse to the point of being cryptic but still earns its line.

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 return values need not be explained, yet the description summarizes them anyway as a bonus. It covers cost, step cap, and all inputs; the notable omission is how this tier relates to the other two agent tools, which matters most for correct selection of a generic agent.

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 load — and it does name all four parameters with intent ('task; optional context, fields for a JSON answer, language'). But it adds no depth: nothing on what shape 'context' should take (string/object/array), what naming convention 'fields' entries should follow, or guidance on the language pattern, leaving real ambiguity for a 0%-coverage schema.

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?

States a concrete capability in a specific verb+resource framing: 'hand it any task in plain words and get the finished result in one call,' reinforced by concrete task examples (research a company, check a website, read the markets) and an explicit 'Up to 10 steps' scope. It partially differentiates itself from the sibling tiers via the step ceiling and price, but never names hubvibe_agent_task or hubvibe_agent_task_max, so the agent must infer the tier tradeoff.

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 conveyed by example — open-ended research, verification, comparison, fact-pulling — which implies when this tool is appropriate. However, there is no explicit when-not guidance and no routing to alternatives, which is a real gap given two sibling agent tiers; the description never says 'use the cheaper/shorter tier for simple lookups or the max tier for deeper work.'

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.