Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Scan a URL in the Aether sandbox

scan_url

Submit a real http(s) URL to the Aether sandbox for a private scan, returning its flow_id; use only when the user explicitly requests a URL scan.

Instructions

Submit a URL to the Aether sandbox as a private scan. Returns its flow_id.

When to use: ONLY when the user explicitly asks to scan a URL in their own message.

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
urlYesReal http(s) URL to scan, not defanged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/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. It usefully discloses that the scan is private and that the call returns a flow_id, implying asynchronous submission rather than an inline verdict. It says nothing about cost, rate limits, latency, or what happens to the URL once submitted, and does not tell the agent the returned flow_id must be fed to a result-fetching step.

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?

Two sentences, both earning their place: the first defines the action and its return value, the second constrains invocation. The key output (flow_id) is front-loaded rather than buried.

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?

With no output schema, mentioning flow_id is the right compensating move, and the parameter is fully covered by the schema. However, for an asynchronous submission tool the description omits the natural follow-up step (retrieving results via get_scan_result using the flow_id), leaving the agent without the full call sequence.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that a real, non-defanged http(s) URL is expected. The description adds no format, encoding, or validation nuance beyond that, which is the baseline for a fully documented single-parameter schema.

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?

States a specific verb and resource ("Submit a URL to the Aether sandbox as a private scan") and names the immediate artifact returned ("flow_id"). It does not distinguish itself from plausible siblings such as lookup_url or scan_file, so an agent cannot fully route between them from this text alone.

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?

Gives an explicit and unusually strict gate: "ONLY when the user explicitly asks to scan a URL in their own message." That is a clear when-to-use condition with an implied when-not (no proactive/opportunistic scanning). It stops short of naming an alternative tool for the non-explicit case, so it is strong but not complete routing guidance.

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