Skip to main content
Glama

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.

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": "audit_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
languageNo

Output Schema

NameRequiredDescriptionDefault
passYes
statusNo
metricsNo
findingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / language / description
      Removed value: -"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."
    • removedInput schema / properties / language / examples
      Removed value: -[
      -  "ja"
      -]
    • removedInput schema / properties / url / description
      Removed value: -"Live, fetchable http(s) URL to audit."
    • removedInput schema / properties / url / examples
      Removed value: -[
      -  "https://example.com"
      -]
    • removedInput schema / title
      Removed value: -"Live URL to audit"
  2. Changed7 schema fields changed
    • 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."
  3. Changed1 schema field changed
    • 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"
      +}
  4. Changed6 schema fields changed
    • 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"
      +}
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile. The description adds meaningful behavioral context beyond that: the audit is based on one real browser load, uses measured rather than estimated values, returns findings for heavy pages, and costs $0.05 per call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: the audit scope and measured metrics come first, followed by a useful scope exclusion and the per-call price. Every sentence carries information, with no redundant phrasing.

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?

The description is largely complete for a read-only audit whose output schema can explain return values, and it covers methodology, scope, findings, and cost. However, it leaves the optional language parameter undocumented, which is a real gap given the schema provides no parameter descriptions.

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

Parameters2/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 clarify both parameters. It only implies that 'url' is the web page being audited and does not explain the optional 'language' parameter at all, leaving a material semantic gap.

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?

The description states a specific verb and resource: a page speed and page weight audit of a web page, with concrete metrics (total bytes, HTTP requests, DOM nodes). It also sharply scopes the tool as page-weight signals rather than Core Web Vitals, which distinguishes it from broader page-audit siblings.

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?

It gives clear usage context by positioning the tool for page-weight and page-speed findings and explicitly excluding Core Web Vitals, so an agent can tell when the tool is appropriate. It does not name sibling alternatives such as audit_bundle or audit_seo, so the alternative-selection guidance is incomplete but still clear.

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.