Skip to main content
Glama
Sign In

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

by ai.urlcheck
OverviewDiscussionsAdmin

url_scanner_async_task_status

Read-only

Check the status of an asynchronous scan task. Returns the current task status using native MCP task semantics (working, completed, failed, cancelled) without blocking. Use url_scanner_async_task_result to retrieve the result once completed.

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": {
      "task_id": "<task_id>"
    },
    "name": "url_scanner_async_task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesThe task ID to check status for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context by specifying the native MCP task semantics (working, completed, failed, cancelled) and the non-blocking behavior. This goes beyond the annotation baseline, though it does not cover error handling or polling details, so a 4 is appropriate.

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?

The description is two sentences, front-loaded with the primary purpose, followed by a concise pointer to the sibling tool. Every word earns its place with no redundancy or filler.

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?

The tool is simple, and the description covers purpose, semantics, and alternative tool usage. The absence of an output schema is mitigated by listing the possible status values. Minor omissions include how the task_id is obtained (implied by sibling async scan tools) and any error conditions, but these are not critical for this straightforward status-check tool.

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% with a single parameter (task_id) already described as 'The task ID to check status for.' The description does not add additional semantics beyond what the schema provides, so the baseline 3 is correct.

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?

The description clearly states the tool's function: 'Check the status of an asynchronous scan task.' It uses a specific verb ('check') and resource ('status'), and explicitly differentiates from the sibling result-retrieval tool by mentioning 'Use url_scanner_async_task_result to retrieve the result once completed.' This is unambiguous and distinguishes it from the other async tools.

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?

The description provides explicit guidance on when to use this tool: to check status without blocking. It also names the alternative (url_scanner_async_task_result) for retrieving results after completion, making the usage context and decision boundary clear.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources