Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Search Aether reports

search
Read-only

Find Aether analysis reports by family, file type, MITRE technique, tag, verdict, filename, registry key, YARA rule, or date range, and paginate recent matches.

Instructions

Search Aether analysis reports by family, file type, signal group, MITRE technique, tag, verdict, file name, registry key, YARA rule and date. Only the 200 newest matches are reachable; to go further back, set date_from and date_to to an earlier range.

When to use: To find samples matching the user's criteria, with exact names from the resolve_* tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (5 files per page, newest report of each).
tagsNoAether tags, comma-separated.
date_toNoEnd date YYYY-MM-DD.
verdictNoFinal verdict.
filenameNoFile name or part of it, any case, e.g. 'invoice'.
filetypeNoOne file type from resolve_file_type.
date_fromNoStart date YYYY-MM-DD.
yara_ruleNoExact YARA rule name, any case, e.g. from get_yara_matches.
registry_pathNoFull registry key path, any case, e.g. 'HKCU\Software\Microsoft\Windows\CurrentVersion\Run'.
signal_groupsNoSignal group IDs from resolve_signal_group, comma-separated.
mitre_techniquesNoMITRE technique IDs from resolve_technique, comma-separated.
threat_attributionNoFamily names from resolve_family, comma-separated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=true, so the description carries the rest, and it does disclose a major non-obvious constraint: only the 200 newest matches are reachable, with date_from/date_to as the escape hatch for older data. That is exactly the kind of behavioral limit an agent would otherwise hit blindly. It does not describe result contents or whether filters combine with AND, leaving a small gap.

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?

Two short paragraphs, front-loaded with capability then usage, with no filler sentences. The result-cap caveat is placed where it matters and is stated in concrete numbers rather than vague hedging.

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 12-parameter all-optional search with no output schema, the definition covers purpose, when to use, prerequisite resolution of enum-like values, and the result ceiling. Missing only minor items such as how filters combine and what a match record contains, which keeps it slightly short of fully complete.

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%, so the baseline is 3; the description adds value by tying parameters to their authoritative sources (exact family, file type, signal group, and technique names from the resolve_* tools) and by explaining the date-range parameters as the mechanism for reaching older-than-200 results. It does not clarify combinations or tag semantics 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?

States a specific verb and resource ("Search Aether analysis reports") and enumerates the filterable dimensions (family, file type, MITRE technique, registry key, YARA rule, date). It also implicitly separates itself from the get_*/lookup_* siblings by framing itself as the criteria-based finder and pointing at resolve_* tools for exact names.

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?

An explicit "When to use" line names the scenario (finding samples matching user criteria) and a prerequisite (obtain exact names via resolve_* tools first). It also gives the workaround for the result cap. It stops short of stating when a different tool is the better choice, so it is clear context rather than full routing guidance.

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