Skip to main content
Glama

Smarty-Pants AI

scan_url

Scan a single URL for phishing or malware risk.

Args:
    url: The URL to scan.
    temperature: Optional decision threshold from 0.0 to 1.0. Higher is
        stricter; when omitted the service default is used.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
temperatureNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does add real value by explaining the temperature threshold semantics and that the service default applies when omitted. It says nothing about latency, network fetch behavior, whether results are cached, or what the verdict structure looks like (partly mitigated by the output schema).

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?

The one-line summary is front-loaded and the docstring-style Args block is compact with no filler. Slightly verbose line wrapping aside, every sentence earns its place.

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 simple two-parameter scan tool with an output schema covering return values, the definition supplies purpose, the required input, and the tuning knob's behavior. The main remaining gap is the lack of explicit routing guidance against the sibling scan_urls tool.

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 description coverage is 0%, so the description has to compensate, and it does for temperature: range 0.0-1.0, direction (higher is stricter), and omission behavior, none of which appear in the schema. The url parameter entry ("The URL to scan") is essentially tautological, which keeps this from a 5.

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 gives a specific verb and resource ("Scan a single URL") plus the risk categories checked (phishing, malware), so the agent knows exactly what the tool produces. The word "single" implicitly separates it from the plural sibling scan_urls, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: "single URL" suggests this is the one-URL path while scan_urls handles batches, but the description never states when to prefer one over the other or any exclusion. No prerequisites, rate-limit context, or fallback guidance is provided.

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