Skip to main content
Glama

Get a website scan's result

get_website_report
Read-onlyIdempotent

The result of an optimize_website call that was still working when it returned. Pass its job_id. Waits up to a minute for the scan to finish.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_website_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id returned by optimize_website.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered; the description goes beyond them by disclosing that the call blocks for up to a minute while waiting. That timing behavior is the single most important thing an agent needs to know before invoking it. It does not say what happens if the minute elapses, which leaves the failure mode opaque.

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?

Three short sentences, front-loaded with the resource, then the required input, then the timing caveat. No filler and nothing buried mid-paragraph.

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?

There is no output schema, so the description carries the burden of explaining what comes back, and 'the result of a scan' is vague about whether that means issues found, a score, a report URL, or raw JSON. The one-minute wait is also left without a stated consequence on timeout. Adequate for invoking the tool, but thin for a result-fetching tool with no return schema.

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 coverage is 100% and the single job_id parameter is documented in the schema as coming from optimize_website. The description's 'Pass its job_id' restates the schema rather than adding format or provenance detail beyond it. With the schema already doing the work, the baseline 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 names a specific resource ('The result of an optimize_website call') and anchors it to a concrete condition (the call was still working when it returned), so the agent knows exactly what is being fetched. The gap is sibling differentiation: get_website_scan and list_website_scans exist and the description never explains how a 'report' differs from a 'scan', which matters given the near-identical naming.

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 clearly states the triggering condition: use this when optimize_website returned a still-running job rather than a finished result. That is real context an agent can act on. It stops short of naming an alternative or saying what to do if the job is gone/expired, so usage guidance is clear but not exhaustive.

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