Skip to main content
Glama

Free scan of a site

scan_site

Runs SniffPup's free passive scan of a live website (takes up to about a minute) and returns the score and the issues found. Every critical issue comes with masked evidence, fix steps and a fix prompt (with no critical issue, one other issue does). The scan is for a site the user owns or has permission to test. It stores a scan and counts toward the free scan allowance. consent records the user's confirmation: I own this site or can test it, and agree to the Terms, including individual arbitration.

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>",
      "consent": "<consent>"
    },
    "name": "scan_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe live site to scan: an http or https URL, or a bare host such as your-app.com (https is assumed). At most 2048 characters. The server refuses other schemes and addresses that include a username or password.
consentYesRecords the user's confirmation: I own this site or can test it, and agree to the Terms, including individual arbitration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / consent / description
      Previous value: -"true only if the user confirmed: I own this site or can test it, and agree to the Terms, including individual arbitration."New value: +"Records the user's confirmation: I own this site or can test it, and agree to the Terms, including individual arbitration."
    • changedInput schema / properties / url / description
      Previous value: -"The live site to scan, like https://your-app.com or your-app.com."New value: +"The live site to scan: an http or https URL, or a bare host such as your-app.com (https is assumed). At most 2048 characters. The server refuses other schemes and addresses that include a username or password."
    • addedInput schema / properties / url / maxLength
      Added value: +2048
    • addedInput schema / properties / url / minLength
      Added value: +1
  2. Changed1 schema field changed
    • changedInput schema / properties / consent / description
      Previous value: -"true only if the user confirmed: I own this site or have permission to test it, and I agree to the Terms (including individual arbitration), Acceptable Use Policy and Privacy Policy. Free scans are passive: we only look at what any visitor's browser can see."New value: +"true only if the user confirmed: I own this site or can test it, and agree to the Terms, including individual arbitration."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare that this is not read-only, is open-world and non-idempotent, and the description is consistent with that by disclosing 'It stores a scan and counts toward the free scan allowance.' It adds valuable behavior beyond annotations: the up-to-about-a-minute runtime, the guaranteed masked evidence/fix steps/fix prompt on critical issues, and the quota cost. It does not describe failure modes or what happens when the allowance is exhausted.

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?

Three sentences, front-loaded with purpose and runtime, then output shape, then legal/quota framing. Dense and largely waste-free, though the consent sentence duplicates schema text almost verbatim and the parenthetical about fix prompts is slightly convoluted.

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

Completeness4/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 the burden of describing returns and does so adequately (score plus issues, with evidence and fix prompts). It also covers runtime, side effects and quota, which are the key unknowns for this tool. Minor gaps remain around error/refusal behavior and what the score represents.

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 the baseline is 3; both url and consent are already thoroughly documented in the schema. The description restates the consent wording and adds the ownership/permission framing that gives consent its meaning, but adds no new syntax or form constraints for url.

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 opens with a specific verb and resource ('Runs SniffPup's free passive scan of a live website') and states the return value ('the score and the issues found'). An agent knows exactly what the tool does and what it produces without opening the schema.

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 states the eligibility condition clearly ('a site the user owns or has permission to test') and notes the scan consumes the free allowance, which shapes when to call it. There are no sibling tools to route against, and the description does not spell out exclusions beyond the consent requirement, so it stops just 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