Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Get YARA matches of a report

get_yara_matches
Read-only

Retrieve YARA rules that matched a file in an Aether report by report ID and SHA-256, returning rule details, verdict, and tags to identify malware families.

Instructions

The relevant YARA rules that matched each file of one report (input, extracted and downloaded): rule, description, author, verdict and tags (e.g. a malware family).

When to use: When the user asks which YARA rules hit a sample.

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": {
      "report_id": "<report_id>",
      "sha256": "<sha256>"
    },
    "name": "get_yara_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
sha256YesSHA-256 of the report's file.
report_idYesAether report ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds real context beyond that: matches span three file sources (input, extracted, downloaded) and the response carries rule, description, author, verdict and tags. It says nothing about result volume, pagination or per-file grouping, so it is not fully transparent.

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, zero waste: the returned-content sentence comes first and the usage trigger second. The parenthetical '(input, extracted and downloaded)' adds scope efficiently rather than padding.

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 fields returned, which is the main thing an agent needs. It leaves out result shape (grouped per file) and pagination, minor gaps for a simple two-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?

Schema description coverage is 100%, so both report_id and sha256 are already documented in the schema; the description adds no further meaning, such as how the sha256 relates to a specific file inside the report. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ('the relevant YARA rules that matched each file of one report') and scopes it precisely to input, extracted and downloaded files, then enumerates the returned fields (rule, description, author, verdict, tags). It does not explicitly distinguish itself from the sibling get_yara_rule, so it stops short of a 5.

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?

There is an explicit 'When to use: When the user asks which YARA rules hit a sample' clause, which gives a clear triggering condition. There are no when-not conditions and no named alternative for retrieving rule bodies, which keeps it out of 5 territory.

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