Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Get malware config

get_malware_config
Read-only

Extract malware configurations—C2 servers, keys, and settings—from up to 20 threat reports in one call, returning per-report configs or errors for sample analysis.

Instructions

The malware configs (C2s, keys, settings) Aether extracted from up to 20 reports in one call: per report, its configs (empty if none) or an error.

When to use: When the user asks for the config, C2 servers or keys of one or more samples, e.g. from a search.

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": {
      "reports": "<reports>"
    },
    "name": "get_malware_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportsYesThe reports, each with its report_id and sha256.

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?

Annotations only declare readOnlyHint, so the description carries the rest and does so usefully: it discloses the partial-failure model (per report, configs — empty if none — or an error) and the 20-report cap. It does not state auth requirements or how errors are surfaced beyond existing at report level.

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 blocks: what it returns first, then when to call it. No filler sentences and the return-shape semantics are front-loaded.

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 compensates by describing the per-report result structure (configs or error), which is what an agent most needs to interpret responses. For a one-parameter read tool with a readOnly annotation, that is close to complete.

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% and the single parameter (reports, each with report_id and sha256) is fully documented in the schema. The description only restates the batching limit of 20, adding little beyond the structured fields; baseline 3 applies.

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 uses a specific verb and resource — "malware configs (C2s, keys, settings) Aether extracted" — and names the source (reports), which separates it from generic IOC or scan siblings. It stops short of explicitly naming a sibling tool it differs from, so it is clear but not fully differentiated.

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?

A dedicated "When to use" line gives a concrete trigger — the user asking for config, C2 servers, or keys of one or more samples, e.g. from a search. It gives no explicit when-not-to-use or alternative tool, but the triggering context is unambiguous.

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