Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Pivot: IOC prevalence

get_ioc_prevalence
Read-only

Count how many recent Aether reports each IOC appears in, broken down by report verdict, to identify rare indicators worth pivoting on versus common shared or noise indicators.

Instructions

How many recent Aether reports each IOC appears in (not all-time totals), counted by report verdict. These are the verdicts of the reports, not of the IOC.

When to use: To pick which IOCs to pivot on: rare ones in malicious reports are good pivots; ones in many reports are shared services or noise.

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

Input Schema

NameRequiredDescriptionDefault
ipsNoIP addresses.
urlsNoFull URLs.
emailsNoEmail addresses.
domainsNoDomain names.

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?

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: counts are limited to a recent window rather than all-time, and the verdict labels belong to the reports rather than to the IOC itself. It does not say how long 'recent' is, nor anything about result shape or ordering, which matters since there is no output schema.

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, front-loaded with what is measured and immediately followed by a labelled 'When to use' paragraph. Every sentence carries information an agent needs; nothing is repeated from the schema or annotations.

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 read-only counting tool with zero required parameters and full schema coverage, the definition covers the essentials: scope, counting unit, verdict attribution, and interpretive guidance. The remaining gap is the undefined 'recent' window and the absence of output shape detail, which the description cannot rely on an output schema to supply.

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% — all four parameters (ips, urls, emails, domains) carry their own descriptions, so the schema does the parameter work. The description adds no per-parameter meaning, no guidance on batching many IOCs per call, and no note on which takes precedence, so it sits at the baseline for full schema coverage.

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 specific operation on a specific resource: counting how many recent Aether reports each IOC appears in, explicitly excluding all-time totals and noting the count is broken out by report verdict. That is materially more precise than the bare name 'get_ioc_prevalence'. It does not name a sibling such as pivot_ioc as the contrasting tool, 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?

Provides an explicit 'When to use' section that frames the tool as a triage step before pivoting, and even explains how to read the output: rare IOCs in malicious reports are good pivots, widely-seen ones are shared infrastructure or noise. It gives no 'when not to use' condition and does not name the downstream pivot tool, so it is strong context rather than complete routing.

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