Skip to main content
Glama

Free count-only quick scan

scan_url
Read-onlyIdempotent

Run a FREE, count-only LaunchTrust quick scan on a public web URL. It runs a quick subset of LaunchTrust's compliance and security checks (frontend secrets, exposed .env/.git files, security headers, HTTPS/HSTS, privacy and terms pages, trackers and cookie consent, AI-interaction disclosure) and returns how many gaps it found, not which ones. The result is unsigned; the count is cached for 15 minutes and not otherwise stored. Which gaps they are, the evidence and how to close them come with LaunchTrust Monitoring (every detector, signed and dated records) or a one-time Launch Audit. Compliance aid, not legal advice.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL to scan, e.g. https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses material behavior: the scan is a subset of detectors, the result is a count rather than a list, output is unsigned, the count is cached for 15 minutes and not otherwise stored. It also adds a scope disclaimer ('Compliance aid, not legal advice'), which matters for how an agent relays results.

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?

It is front-loaded with the core action and scope, then layers detector list, output limits, caching, and upsell in a logical order with no filler sentences. The detector enumeration and commercial framing make it denser than strictly necessary, but each clause carries information.

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 one-parameter, no-output-schema tool, the description supplies everything an agent needs: input constraint (public http(s) URL), what is returned (a gap count, not the gaps), freshness (15-minute cache), trust level (unsigned), and where to go for detail. No meaningful gap remains.

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?

With a single parameter and 100% schema description coverage, the schema already carries the meaning ('Public http(s) URL to scan, e.g. https://example.com'). The description's mention of 'public web URL' largely restates that, adding only the implicit constraint that non-public or internal targets are out of scope.

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 definition opens with a specific verb and resource — 'Run a FREE, count-only LaunchTrust quick scan on a public web URL' — and enumerates the check categories covered, so the agent knows exactly what the tool produces. It clearly separates itself from the paid depth options (Monitoring, Launch Audit), though it never explicitly contrasts with the sibling scan_app, leaving that boundary to inference.

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 a clear condition for use: a free, quick, count-only look at a public URL, and explicitly routes anyone who needs the actual gaps, evidence, or remediation to Monitoring or a one-time Launch Audit. There is no explicit when-not-to-use rule or named sibling alternative, which keeps it short of a 5.

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.

Resources