Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Look up URLs

lookup_url
Read-only

Check the reputation of up to 100 URLs in one call, returning per-URL verdicts, MD Cloud detections, and recent sandbox reports before scanning.

Instructions

Aether's reputation for up to 100 URLs in one call: per URL, verdict (may reflect the files that contain it), MD Cloud detections and a few recent sandbox reports of files that contain it (report_id, flow_id). More: pivot_ioc.

When to use: To check URLs. Try this before scan_url.

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": "lookup_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesFull URLs, e.g. ['https://example.com'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Adds useful context beyond readOnlyHint: the returned fields (verdict, MD Cloud detections, sandbox report_id/flow_id) and an important caveat that the verdict 'may reflect the files that contain it'. However, it does not say what happens when a URL is unknown/unseen, whether results are cached or fresh, or anything about rate limits, so the behavioral picture is partial rather than complete.

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?

Front-loads the return-content summary, then caveat, then usage — well ordered and short. The line 'When to use: To check URLs' is largely redundant with the first sentence and could be dropped.

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?

With no output schema, the description carries the return-value burden and does so adequately by enumerating the verdict/detections/report fields. A note on unseen or invalid URL handling is the main remaining gap for a one-parameter read 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?

Only one parameter and the schema already documents it at 100% coverage ('Full URLs, e.g. [https://example.com]'), so the schema does the heavy lifting. The description's 'up to 100 URLs in one call' merely echoes maxItems and adds no format or normalization guidance.

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?

Names a specific operation (Aether reputation lookup) on a specific resource (URLs) with batching scope ('up to 100 URLs in one call'), and explicitly separates itself from scan_url and points to pivot_ioc for the related pivot direction.

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?

States 'When to use: To check URLs' and gives a concrete ordering rule — 'Try this before scan_url' — which is real selection guidance. The when-to-use clause itself is close to a restatement of the purpose, and no explicit case is given for skipping this in favor of scan_url.

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