Skip to main content
Glama
Sign In

Web Scan

by io.github.ankitkumarjha515
OverviewDiscussionsAdmin

Get a stored report

get_report
Read-only

Read a stored Web Scan report by its slug (the part after /r/ in an agentmarket.lol/web-scan/r/ link) without re-scanning: score, grade, scan time and the failing or warning checks with fixes. Use this when the user shares a report link. Reports expire after two weeks; to check the current state of a site, use scan_url or verify_fixes instead.

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": {
      "slug": "<slug>"
    },
    "name": "get_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesReport slug, e.g. "k3m9p2x7qa", or the full report URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and closed-world, so safety is covered. The description adds real context: no re-scan occurs, what fields are returned, and that reports expire after two weeks. It stops short of describing error behavior for an expired or unknown slug, which is the remaining gap.

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?

Two sentences, front-loaded with the verb and resource, then the routing rule. Every clause carries information: slug format, returned contents, expiry, and alternatives, with no filler.

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?

For a one-parameter read tool with full schema coverage and no output schema, this is nearly complete: it describes return contents inline. Only the expired/invalid-slug outcome is unspecified, a minor gap given the simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline applies, but the description adds meaning beyond the schema by explaining where the slug comes from ('the part after /r/ in a .../web-scan/r/<slug> link'). That materially helps an agent extract the value from user-supplied URLs.

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?

States a specific verb and resource ('Read a stored Web Scan report by its slug'), defines what the slug is, and enumerates the returned content. An agent can distinguish it from the sibling scan tools without inspecting 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 Guidelines5/5

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

Explicitly says when to use it ('when the user shares a report link') and names the alternatives with the condition that selects them ('to check the current state of a site, use scan_url or verify_fixes instead'). It also notes the two-week expiry, which affects the use/don't-use decision.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Web Scan toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources