Skip to main content
Glama
omeryemba

mcp-hayabusa

by omeryemba

analyze_coverage

Assess ATT&CK detection coverage by analyzing installed Sigma rules. Identifies weakly covered techniques with a sorted breakdown, or checks coverage for a specific technique ID.

Instructions

Analyze ATT&CK detection coverage across the installed Sigma rule set.

With no technique_id, returns an overall breakdown of how many rules cover each ATT&CK technique/tactic referenced anywhere in the rule set, sorted ascending by rule count so the weakest-covered techniques/tactics are easy to spot. With technique_id, returns a focused answer for just that one technique instead (rule_count 0 / covered=False if no installed rule references it -- not an error, a normal coverage answer).

IMPORTANT: coverage here means "referenced by tags on installed rules," not a gap analysis against the full MITRE ATT&CK matrix -- no MITRE reference dataset is bundled, so this cannot report techniques with zero rules across all of ATT&CK, only the distribution across what is actually installed. See coverage_scope in the result for this caveat.

Args: technique_id: Optional single ATT&CK technique ID (e.g. "T1059.001") to report focused coverage for instead of the full breakdown. rules_dir: Optional path to a rules directory. Defaults to the "rules" directory next to the resolved hayabusa binary. max_items: Maximum number of techniques/tactics to include in the overall breakdown lists (default 200). Ignored when technique_id is given.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_itemsNo
rules_dirNo
technique_idNo
Behavior4/5

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

With no annotations, the description carries full burden. It explains coverage is based on tags, that returning rule_count 0 is normal, and mentions coverage_scope field. Minor omissions: not stating read-only nature or permissions, but overall transparent.

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?

Well-structured with main purpose, behavior details, important caveat, and Args list. Every sentence adds value, though slightly verbose. Good front-loading of key info.

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?

No output schema, but description adequately describes return structure (overall breakdown or focused answer, coverage_scope field). Sufficient for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description fully explains all three parameters: technique_id (focused vs full), rules_dir (default path), and max_items (default, ignored with technique_id). Adds significant context beyond schema.

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

Purpose5/5

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

The description clearly states it analyzes ATT&CK detection coverage across installed Sigma rules. It distinguishes behavior with and without technique_id, and implicitly differentiates from sibling tools like search or suggest_rule by focusing on coverage analysis.

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 description provides clear context and an important caveat explaining what coverage means (tags on installed rules, not full ATT&CK matrix). However, it does not explicitly state when to avoid this tool or mention specific alternatives among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/omeryemba/mcp-hayabusa'

If you have feedback or need assistance with the MCP directory API, please join our Discord server