Skip to main content
Glama

launchfiles_live_drift_check

Read-onlyIdempotent

Run a live HTTP, legal, sitemap, and Stripe Checkout / seller-brand drift inspection on a public website.

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

Input Schema

NameRequiredDescriptionDefault
urlYesLive https:// homepage URL to inspect for checkout and trust drift.
expectedBrandTokensNoOptional lowercase brand tokens expected on Stripe checkout surfaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered structurally. The description adds useful context beyond that by specifying it performs live network inspection across several distinct surfaces, but it leaves notable gaps: it does not say whether the Stripe Checkout probe creates real checkout sessions, how long a live crawl takes, or what constitutes a 'drift' finding. For a tool whose name mentions Stripe Checkout, the absence of any clarification that nothing is purchased or mutated is a meaningful omission.

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 sentence with the action and the full set of inspected surfaces front-loaded; there is no filler or redundant restatement of the title. The dense noun stack ('HTTP, legal, sitemap, and Stripe Checkout / seller-brand drift') is slightly hard to parse but every element carries 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 only two well-documented parameters and annotations covering the safety profile, the definition is close to complete for invocation. The gap is on the outcome side: there is no output schema and no description of what the inspection returns or how findings are categorized, so an agent cannot anticipate the report shape for a multi-surface 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 the url and expectedBrandTokens parameters are already documented with their format and purpose. The description adds no additional semantics for either parameter, such as what happens when expectedBrandTokens is omitted or how token matching is evaluated. Baseline 3 applies when the schema does the heavy lifting.

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?

The description names a concrete verb ('Run ... inspection') and a concrete resource ('a public website'), then enumerates the checked surfaces: HTTP, legal, sitemap, and Stripe Checkout / seller-brand drift. That scope is distinguishable from siblings like seo_audit or ux_audit, which target different concerns. It loses a point only because 'drift' is not defined, so the agent must infer what 'drift' means in practice.

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

Usage Guidelines3/5

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

Usage is implied by the word 'live' and by the enumeration of checks (verifying a deployed site's checkout and trust surfaces match expectations). However, the description gives no explicit when-to-use guidance, no prerequisites, and does not mention any sibling tool as an alternative for overlapping audits such as seo_audit or ux_audit.

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.