Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Get scan result

get_scan_result
Read-only

Retrieve the verdict, file, tags, and report ID for a scan started with scan_file or scan_url, then poll with the returned flow ID until the scan finishes.

Instructions

Get the verdict, file and tags of a scan started with scan_file or scan_url, and its report_id for the get_* report tools (has_config: a malware config was extracted).

When to use: After scan_file or scan_url, with their flow_id. Call again while finished is false.

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": {
      "flow_id": "<flow_id>"
    },
    "name": "get_scan_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
flow_idYesThe flow_id returned by scan_file or scan_url.
wait_secondsNoWait up to this many seconds for the scan to finish.
signal_groupsNoAlso return the signal groups (sandbox indicators, incl. YARA and OSINT) that explain the verdict. Larger: only to explain the verdict.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the weight, and it does disclose the polling lifecycle (repeat while finished is false) and the cost/size tradeoff of signal_groups. It does not mention flow_id lifetime/expiry or what happens when a scan fails or the id is unknown, which are the remaining behavioral gaps.

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, front-loaded with the return payload before usage guidance, and the parenthetical is the only compression device used. Nothing is repeated and no sentence is 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?

With no output schema, the description usefully enumerates the key returned fields (verdict, file, tags, report_id, has_config) and notes that signal_groups expands the payload to sandbox indicators. It is nearly complete for a polling tool; only error/empty-result behavior is unstated.

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%, so all three parameters are already documented in the schema, including wait_seconds' bound and signal_groups' 'larger' caveat. The description only reinforces existing meaning ('with their flow_id') and explains the returned report_id rather than the inputs, so it adds little beyond the schema.

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 names the specific verb and resource ('Get the verdict, file and tags of a scan') and ties it to the producing tools (scan_file/scan_url), so an agent can distinguish it from the get_* report tools it also mentions. The parenthetical explains 'has_config' inline, removing ambiguity about one of the returned fields.

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?

An explicit 'When to use' clause names the prerequisite (a prior scan_file or scan_url plus its flow_id) and gives the polling rule ('Call again while finished is false'). It also routes the agent to the get_* report tools for deeper detail, so the boundary between this summary tool and the report tools is stated rather than inferred.

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