vibefix

vibefix_diagnose

Scan any public URL for performance, accessibility, SEO, and best practices issues. Get scores and a list of problems with one-click bounty pre-fill to post fix requests.

Instructions

Run a free diagnostic scan on any public URL. Returns performance, accessibility, SEO, and best practices scores plus a list of issues found — each with a ready-made bounty pre-fill so the user can post a fix request in one click. No API key required.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	The public URL to scan (e.g. "https://example.com")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Apr 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description provides key behavioral details: it returns scores and issue lists, and includes a ready-made bounty pre-fill. It also states it's free and no API key required. However, it does not mention error handling or behavior for invalid URLs.

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?

Two sentences, no wasted words. The first sentence states the primary action, the second details the outputs. Information is front-loaded and efficiently organized.

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

Completeness5/5

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

For a simple tool with one parameter and no output schema, the description adequately covers what it does, what it returns, and prerequisites (public URL, no API key). The agent can correctly select and invoke this tool based on the description alone.

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?

The schema covers the 'url' parameter with 100% description. The tool description adds value by clarifying it accepts any public URL, providing an example format, and explaining what the output includes (scores, issues, bounty pre-fill).

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 clearly states the tool runs a diagnostic scan on a public URL, listing specific categories (performance, accessibility, SEO, best practices) and outcomes (scores and issues with bounty pre-fill). It distinguishes itself from sibling tools that handle bounties and submissions.

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?

The description mentions it's free, no API key required, and for any public URL. It implies when to use (for diagnosing a URL) but does not explicitly state when not to use or mention alternative tools. The context is clear enough for most scenarios.

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

Deploy Server