Skip to main content
Glama

Smarty-Pants AI

scan_urls

Scan several URLs in one request.

Args:
    urls: The URLs 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": {
      "urls": "<urls>"
    },
    "name": "scan_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes
temperatureNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and mostly doesn't. It discloses that all URLs are handled in one request and that a service default applies when temperature is omitted, but says nothing about read-only vs. mutating behavior, partial failure handling when some URLs fail, rate limits, or auth requirements — all material for a batch network operation.

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 appropriately short, and the Args block is compact. The formatting is a raw docstring dump and the urls line ("The URLs to scan") adds no information, but there is no real padding.

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?

Because an output schema exists, return values needn't be described, and both parameters get some coverage. Still, for a batch tool with zero annotations and zero schema descriptions, the definition leaves notable gaps: what a scan actually determines, and what happens when individual URLs in the batch fail.

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 must compensate and largely does: temperature is explained beyond the schema with its range (0.0–1.0), direction ("higher is stricter"), and fallback ("service default is used"), none of which the schema conveys. The urls entry is essentially a restatement of the parameter name, which is the only weak spot.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first line states a verb ("Scan") and a resource ("several URLs") plus the batching behavior ("in one request"), which is informative. However, "scan" is never defined — an agent cannot tell whether this is a security scan, content classification, or reachability check — and the definition never distinguishes itself from the sibling scan_url beyond the word "several".

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 when-to-use guidance: nothing says when to prefer this batch tool over scan_url or get_usage, no prerequisites, and no constraint such as a maximum URL count. The only conditional behavior mentioned is the temperature default, which is parameter semantics rather than usage guidance.

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