Skip to main content
Glama

Scan a website's software now

scan_website_software
Idempotent

Scans the monitor's website for the software it runs and checks it against the vulnerability sources now, instead of waiting for the next scan. Takes up to a minute; then read get_vulnerabilities. Free.

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": {
      "id": "<id>"
    },
    "name": "scan_website_software"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already show readOnlyHint=false, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the agent knows this triggers external work without destroying anything. The description adds context the annotations do not carry: the run can take up to a minute, it is free, and the result is read through get_vulnerabilities rather than a return value. It does not describe what happens on failure, on a duplicate request, or on rate limiting, but it covers the essentials.

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 clauses, each carrying distinct information, with the time, cost, and follow-up all front-loaded or packed into one line. There is no filler and no repeated wording.

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 an asynchronous trigger tool with no output schema, the description supplies the pieces the agent needs: latency expectation, the follow-up call that produces the results, and the fact that it costs nothing. It stops short of covering error handling or concurrent-scan behavior, but it is sufficient to call the tool correctly.

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?

The single required parameter 'id' already has 100% schema description coverage, with a UUID format and a pointer to list_monitors as the source. The description adds nothing further about the parameter, which is acceptable because the schema fully documents it, but that leaves the baseline score appropriate.

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 verb and resource: scanning the monitor's website for installed software and matching it against vulnerability sources. What makes it distinct is the explicit on-demand timing ('now, instead of waiting for the next scan'), which separates it from a passive check. It never names check_website or scan_ports, so the agent must infer the boundary between these similar-sounding tools.

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?

The phrase 'now, instead of waiting for the next scan' clearly states the condition that should trigger this tool: an immediate, on-demand refresh rather than the normal cycle. It also gives the follow-up step ('then read get_vulnerabilities'). It gives no explicit case against using it, such as when a scan is already in progress or when the cached result is enough.

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