Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

List signal groups

resolve_signal_group
Read-only

Retrieve Aether signal group IDs and titles matching keywords so you can map sample behavior to relevant sandbox indicators before searching.

Instructions

Get Aether's signal group IDs (sandbox indicators) with their title, matching a query.

When to use: Before searching by a sample behavior, to get the matching signal group IDs.

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_signal_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoKeywords for the group ID or title, with synonyms (any matches), e.g. ['keylog', 'keystroke']. Omit for all (large).

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 tells the agent this is a safe read. The only extra behavioral facts — synonym matching and that omitting the query returns everything (large) — are already stated in the schema, so the description adds little beyond structured fields, and says nothing about result size or truncation behavior.

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: what it returns first, then the usage cue. No filler, no repetition of the title, and the key information is 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?

For a single-optional-parameter read-only resolver with no output schema, the definition covers what comes back (IDs plus titles) and the invocation precondition. Minor gaps remain around output volume/pagination when the query is omitted and how the IDs feed into downstream tools.

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 query parameter already documents synonyms, any-match semantics, an example, and the omit-for-all behavior. The description's "matching a query" restates rather than extends that, so the baseline of 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?

States a concrete verb+resource: retrieve Aether signal group IDs with titles, filtered by a query, and clarifies what a signal group is ("sandbox indicators"). It does not distinguish itself from sibling resolver tools like resolve_family or resolve_technique, so an agent must infer the boundary.

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?

The "When to use" line gives a clear ordering cue: call this before searching by a sample behavior in order to obtain the IDs. It stops short of naming the follow-up tool (e.g., search vs find_similar) or stating when not to use it, so the alternative is implied rather than explicit.

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