Skip to main content
Glama

PreClick — An MCP-native URL preflight scanning service for autonomous agents (formerly URLCheck).

by ai.urlcheck

url_scanner_scan

Read-only

Analyze a URL for security threats (synchronous, blocks until complete or timeout). Returns risk score, confidence, agent access guidance, and intent_alignment (always not_provided for this tool; use url_scanner_scan_with_intent for intent context). For long-running scans, prefer url_scanner_async_scan which returns immediately with a task_id for polling via url_scanner_async_task_result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to analyze. Must be HTTP or HTTPS. If no scheme provided, https:// is assumed.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=true), the description discloses synchronous blocking behavior, timeout, and return fields (risk score, confidence, agent access guidance, intent_alignment). It also states that intent_alignment is always not_provided, which is a key behavioral trait.

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?

Description is two sentences, front-loaded with purpose and key behavior, then immediately provides guidance on alternatives. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description explicitly lists return fields. It covers synchronous behavior, safety profile (via annotations), and alternative tools, making it complete for an agent to select and invoke 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?

Schema provides 100% coverage with a clear description of the url parameter, including scheme assumptions and encoded/unencoded handling. The description adds no new parameter semantics, so baseline score of 3 is appropriate.

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

Purpose5/5

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

Description states a specific verb and resource: "Analyze a URL for security threats." It clearly distinguishes from siblings by noting synchronous behavior and absence of intent context ("intent_alignment (always not_provided for this tool)").

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

Usage Guidelines5/5

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

Explicit guidance is provided: "For long-running scans, prefer url_scanner_async_scan" and "use url_scanner_scan_with_intent for intent context." This tells the agent when to use this tool versus alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PreClick — An MCP-native URL preflight scanning service for autonomous agents (formerly URLCheck). toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

The tools are clearly grouped into synchronous and asynchronous scanning pairs with intent variants, making their purposes distinct. However, the async status and result tools could be slightly confusing as separate tools when they serve closely related polling functions.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with clear prefixes (url_scanner_) and descriptive suffixes (async_scan, scan_with_intent, async_task_status). The naming is highly predictable and systematic throughout.

Tool Count5/5

With 6 tools, the server provides a well-scoped set that covers both synchronous and asynchronous scanning workflows, including intent variants and polling mechanisms. This count is appropriate for a focused URL scanning service.

Completeness5/5

The tool set offers complete coverage for URL scanning: synchronous and asynchronous modes, with and without intent, plus status checking and result retrieval. There are no obvious gaps for the domain, supporting full agent workflows without dead ends.

Resources