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

Page performance audit

audit_performance

Read-onlyIdempotent

Page speed and page weight audit of a web page from one real browser load: total bytes transferred, HTTP request count and DOM node count, measured rather than estimated, with findings when the page is heavy. Page-weight signals, not Core Web Vitals. $0.05 per call. Returns: pass (bool), metrics{}, findings[] with id/severity/detail.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Live, fetchable http(s) URL to audit.
`language`	No	Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable text of the findings is returned in this language; rule ids, severities, URLs and numbers are untouched. Default: English.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`pass`	Yes
`status`	No
`metrics`	No
`findings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 1, 2026

removedOutput schema / properties / findings / description

Removed value: -"One entry per rule that did not pass. Empty when the check is clean."

removedOutput schema / properties / findings / items / properties

Removed value: -{
-  "detail": {
-    "description": "What failed and where.",
-    "type": "string"
-  },
-  "id": {
-    "description": "Stable rule identifier.",
-    "type": "string"
-  },
-  "severity": {
-    "description": "Rule severity.",
-    "type": "string"
-  }
-}

removedOutput schema / properties / findings / items / required
```
Removed value: -[
-  "id"
-]
```
removedOutput schema / properties / findings / items / type
```
Removed value: -"object"
```

removedOutput schema / properties / metrics / properties

Removed value: -{
-  "dom_node_count": {
-    "minimum": 0,
-    "type": "integer"
-  },
-  "request_count": {
-    "minimum": 0,
-    "type": "integer"
-  },
-  "total_bytes_transferred": {
-    "minimum": 0,
-    "type": "integer"
-  }
-}

removedOutput schema / properties / pass / description

Removed value: -"Whether every rule in this dimension passed."

removedOutput schema / properties / status / description
```
Removed value: -"Present only on a completed audit."
```

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable text of the findings is returned in this language; rule ids, severities, URLs and numbers are untouched. Default: English.",
+  "examples": [
+    "ja"
+  ],
+  "maxLength": 35,
+  "pattern": "^[A-Za-z]{2,3}(-[A-Za-z0-9]{2,8})*$",
+  "type": "string"
+}

Changed6 schema fields changedAug 25, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / url / description

Previous value: -"Live URL to audit"New value: +"Live, fetchable http(s) URL to audit."

addedInput schema / properties / url / examples
```
Added value: +[
+  "https://example.com"
+]
```
addedInput schema / properties / url / format
```
Added value: +"uri"
```
addedInput schema / title
```
Added value: +"Live URL to audit"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "properties": {
+    "findings": {
+      "description": "One entry per rule that did not pass. Empty when the check is clean.",
+      "items": {
+        "properties": {
+          "detail": {
+            "description": "What failed and where.",
+            "type": "string"
+          },
+          "id": {
+            "description": "Stable rule identifier.",
+            "type": "string"
+          },
+          "severity": {
+            "description": "Rule severity.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "metrics": {
+      "properties": {
+        "dom_node_count": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "request_count": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "total_bytes_transferred": {
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "pass": {
+      "description": "Whether every rule in this dimension passed.",
+      "type": "boolean"
+    },
+    "status": {
+      "const": "ok",
+      "description": "Present only on a completed audit.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "pass"
+  ],
+  "type": "object"
+}

First observedAug 11, 2026

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/non-destructive, so safety is covered. The description adds real context beyond them: cost ($0.05 per call), the measured-not-estimated behavior, findings emitted only when the page is heavy, and the return shape.

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?

Very dense and front-loaded: scope, metrics, exclusion, pricing, and return shape in a few clauses. Slightly run-on due to comma stacking, costing a little readability.

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?

Given an output schema already exists, repeating the return fields is mildly redundant, but the description supplies the pricing, the measurement basis, and the non-CWV scope that structured fields do not convey. Adequate for a 2-param read-only audit.

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 100%, so both parameters (url, language) are already fully documented in the schema. The description adds no syntax or format detail about them, so the baseline of 3 is correct.

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?

States a specific verb+resource (page speed and page weight audit of a web page) and enumerates the measured metrics (total bytes, HTTP request count, DOM node count). It clearly distinguishes itself from the sibling audit_bundle/audit_seo/audit_wcag family by scoping to page-weight signals.

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?

Explicitly tells the agent this covers page-weight signals, not Core Web Vitals, and that it works from one real browser load (measured, not estimated). That is a clear when-to-use/when-not signal, though it never names a sibling alternative for the excluded case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.