Skip to main content
Glama

launchfiles_homepage_roast

Read-onlyIdempotent

Run a live 5-second clarity roast + server HTML + checkout drift check on any public homepage, persisting the receipt while keeping response screenshots compact by default.

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_homepage_roast"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesLive https:// homepage URL to roast.
include_screenshotsNoInclude base64 desktop/mobile JPEG data URLs (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the bar is lower; the description still adds that a receipt is persisted and that screenshots are excluded by default to keep responses compact, which is genuine response-shape information. One tension worth noting: 'persisting the receipt' implies server-side state being written despite readOnlyHint=true, though this most likely refers to the service's own record-keeping rather than caller data.

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?

A single sentence with no filler, front-loading the action and following with the response-size default. Nothing could be removed without losing information.

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 carries responsibility for hinting at return values, and it only says screenshots are compact by default. It never explains what the 'receipt' contains or what the roast/drift findings look like, leaving an agent unsure what to expect from a three-part analysis.

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% and both parameters are fully documented in the schema, including the include_screenshots default. The description's 'public homepage' qualifier and 'compact by default' phrasing merely restate the schema's url constraint and default, adding no format or syntax detail.

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 composite action: a 5-second clarity roast, server HTML retrieval, and checkout drift check on a public homepage. The resource and scope are concrete enough to distinguish it from siblings like launchfiles_ux_audit or launchfiles_live_drift_check, though the term 'roast' is slang that an agent must interpret, and bundling three checks into one verb blurs the single purpose.

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?

The only usage signal is the implicit constraint 'any public homepage' (https). There is no guidance on when to pick this over the closely overlapping siblings launchfiles_live_drift_check or launchfiles_ux_audit, and no prerequisites or exclusions 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.