Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

List malware families

resolve_family
Read-only

Retrieve the exact Aether malware family name before running a family search, ensuring queries use the correct spelling.

Instructions

The malware family names Aether attributes (exact spelling for search).

When to use: Before searching by family, to get its exact Aether name.

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": "resolve_family"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already establishes this is a safe, non-mutating lookup, so the description's burden is light. It adds that the returned value is the exact spelling needed for search, which is genuinely useful behavioral context. It does not say how many families come back, whether the list is exhaustive, or how results are ordered.

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 lines, with the when-to-use guidance clearly labelled and placed after the identification sentence. Nothing is padded. The first sentence's grammar is slightly mangled, which costs a point on polish but not on efficiency.

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 zero-parameter read-only lookup with no output schema, the description supplies what an agent needs: what it returns (exact family names) and why to call it (before searching by family). A note on whether the list is complete or paginated would close the remaining gap, but that is minor at this complexity.

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 tool takes zero parameters and the schema has an empty properties object, so there is nothing for the description to clarify. Baseline 4 applies; the description correctly implies a no-argument call.

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 identifies the resource as the malware family names that Aether attributes, and the exact-spelling detail narrows it to a name-resolution tool rather than a search. The verb 'List' lives in the title rather than the description, and the opening clause is a sentence fragment, so it is clear but slightly less crisp than a full verb+resource statement.

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 trigger: use it before searching by family, to obtain the exact Aether name. That effectively routes the agent away from passing a guessed family string straight into search. There is no explicit 'don't use this for' statement, but the sequencing guidance covers the main decision.

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