Skip to main content
Glama

A website scan's status, totals and downloads

get_website_scan
Read-onlyIdempotent

Where a scan stands, what it found and saved, and the download addresses of its ZIP, replacement maps and reports. In totals.bytes, estimated_savings is a prediction; optimized_from and optimized_to are measured. Reads only.

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": {
      "scan_id": "<scan_id>"
    },
    "name": "get_website_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
scan_idYesThe scan's id, from list_website_scans or the web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so 'Reads only' is largely redundant. What the description does add beyond the annotations is data semantics: it distinguishes predicted values (estimated_savings) from measured ones (optimized_from/optimized_to), which materially affects how an agent should report these numbers.

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?

Two compact sentences with no filler, and the payload list is front-loaded. The second sentence leans on backticked field paths that reference a return shape with no output schema to anchor them, which slightly reduces scannability but does not waste words.

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 annotation coverage and no output schema, the description adequately covers both the returned artifacts and the interpretation of key numeric fields. It is missing only edge behavior — for example what is returned while a scan is still running or for an unknown scan_id.

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?

There is a single parameter at 100% schema description coverage, and that schema text already explains that scan_id comes from list_website_scans or the web app. The description adds nothing about the parameter, so the baseline of 3 applies.

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 states concretely what the tool surfaces — a scan's status, the totals it found, and the download addresses for ZIP, replacement maps and reports — so an agent knows the resource and payload. It does not, however, differentiate itself from siblings like get_website_report or get_replacement_mapping, which overlap on reports and mappings.

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?

There is no explicit when-to-use guidance, no statement of prerequisites, and no mention of alternatives. An agent must infer from the sibling list that this is the status/download-URL call and that get_website_report is the detailed report call. The only hint about sourcing the id lives in the input schema, not the description.

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