Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Look up file hashes

lookup_hash
Read-only

Check the reputation of up to 100 file SHA-256 hashes in one call, returning verdicts, malware detections, and recent sandbox reports before file scanning.

Instructions

Aether's reputation for up to 100 file SHA-256s in one call: per hash, verdict, MD Cloud detections and a few recent sandbox reports (report_id, flow_id).

When to use: To check known SHA-256s. Try this before scan_file.

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": {
      "sha256s": "<sha256s>"
    },
    "name": "lookup_hash"
  }
}

Input Schema

NameRequiredDescriptionDefault
sha256sYesSHA-256s of the files.

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?

readOnlyHint=true already tells the agent this is a safe non-mutating call, and the description adds value beyond that by disclosing the batch cap (100 per call) and the shape of results: per-hash verdict, MD Cloud detections, and a few recent sandbox reports with report_id and flow_id. It does not say what happens for hashes with no known reputation or whether results are ordered to match input, which keeps it from a 5.

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 sentences, with the capability and return contents front-loaded and the usage rule immediately after. Every clause carries information; there is no restatement of the tool name 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?

With one parameter, no output schema, and only readOnlyHint for annotations, the description covers the essentials an agent needs: what is looked up, the batch limit, what comes back, and the ordering against scan_file. It is nearly complete; the only notable omission is behavior for hashes absent from the reputation database.

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?

Schema coverage is 100% and maxItems/minItems already encode the batch limits, so the schema carries most of the load. The description still adds meaning by framing the array as a batch checked 'in one call' and by tying the single sha256s parameter to per-hash output records, clarifying that results map back to individual hashes rather than one aggregate verdict.

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 a specific operation on a specific resource: batch reputation lookup for file SHA-256s, returning verdict, MD Cloud detections, and recent sandbox reports per hash. This is distinct from scan_file and from lookup_file/lookup_domain/lookup_ip siblings, so an agent can identify the tool without opening the schema.

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?

It gives an explicit 'When to use' line for known SHA-256s and states a preference ordering: 'Try this before scan_file.' That is a real routing rule rather than implied usage. It stops short of an explicit when-not (e.g. what to do with an unknown or non-SHA-256 identifier), so it is clear context without full exclusions.

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