Skip to main content
Glama

launchfiles_ux_audit

Read-onlyIdempotent

Run LaunchFiles' live Chromium 12-gate Design & UX Radar across desktop (1440x900) and mobile (390x844), returning measured tap-target, landmark, CTA, and hero redesign diagnosis.

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

Input Schema

NameRequiredDescriptionDefault
urlYesLive https:// URL to inspect in Chromium.
override_archetype_idNoOptional trade archetype override ID.
include_visual_payloadsNoInclude base64 screenshots and generated hero artwork data URLs (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description does add real behavior: the page is rendered in a live Chromium instance at two fixed viewports (1440x900, 390x844) and produces measured findings rather than a subjective opinion. It omits runtime expectations, whether the fetch can fail on bots/CSP, and how large the response is when visual payloads are involved.

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?

A single front-loaded sentence with the action first and the outputs trailing, and no wasted clauses. It is dense with branded terminology ('12-gate', 'Radar') that consumes space without informing the agent, which keeps it short of a 5.

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?

With no output schema, the description is the only signal about return values, and it gives only a four-item teaser (tap-target, landmark, CTA, hero diagnosis) without structure, scoring, or whether a report URL versus inline text comes back. For a browser-driven audit tool with an optional base64 screenshot mode, an agent is left guessing about response size and shape.

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 coverage is 100%, so all three parameters (url, override_archetype_id, include_visual_payloads) are already documented in the schema. The description mentions desktop/mobile viewports but does not explain the archetype override or how visual payloads affect the result, so it adds no meaning beyond the schema; baseline 3 applies.

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 specific verb and resource: run a live Chromium 'Design & UX Radar' audit and return tap-target, landmark, CTA, and hero diagnosis, with desktop/mobile viewports named. This is distinguishable from siblings like launchfiles_seo_audit or launchfiles_live_drift_check by its design/UX focus, though the proprietary phrase '12-gate' carries no meaning an agent can act on.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, or alternative-routing guidance. An agent must infer from the words 'Design & UX' that this is the right pick over launchfiles_homepage_roast or launchfiles_seo_audit, and no prerequisites (page must be publicly reachable, audit duration, cost) are stated.

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.