Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Scan a file in the Aether sandbox

scan_file

Upload a local file up to 100 MB as a private scan and get a flow ID to analyze it for threats.

Instructions

Upload a local file (max 100 MB) to the Aether sandbox as a private scan. Returns its flow_id.

When to use: ONLY when the user explicitly asks to scan a file 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": {
      "path": "<path>"
    },
    "name": "scan_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFull local path of the file to scan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full behavioral burden. It usefully discloses upload, 100 MB cap, private scan, and flow_id return, but omits auth needs, rate limits, and async/result-handling behavior, leaving meaningful 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 short paragraphs, with purpose and return value front-loaded, followed by a precise usage condition. Every sentence earns its place and there is no redundant wording.

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?

For a one-parameter upload tool with no output schema, the description supplies purpose, max size, privacy model, return handle, and usage gate. It could say more about the async scan lifecycle or result retrieval, though get_scan_result is a sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents the single path parameter at 100% coverage, so baseline would be 3. The description adds 'local file' and a 100 MB maximum, a real constraint absent from the schema, so it adds meaning beyond the structured parameter.

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 the exact action (upload a local file to the Aether sandbox) and scope (private scan) plus return value (flow_id). The phrase 'local file' distinguishes it from URL-oriented siblings such as scan_url.

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 precondition: ONLY when the user explicitly asks to scan a file in their own message. It does not name scan_url or other alternatives, so routing guidance is clear but not complete.

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