Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Get a YARA rule

get_yara_rule
Read-only

Retrieve an Aether YARA rule’s meta, strings, and condition by exact rule name to inspect what a match detects or how the rule works.

Instructions

The source of an Aether YARA rule (meta, strings and condition), by its exact name.

When to use: When the user wants to see a rule from get_yara_matches, or what it looks for.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact rule name, e.g. from get_yara_matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the description's main added value is disclosing the payload shape (meta, strings, condition) and that lookup is by exact name rather than a fuzzy or partial match. It says nothing about behavior on a missing rule name (error vs. empty result), which matters for an exact-match lookup.

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 sentences, front-loaded with what is returned and followed by the usage condition; no filler. The phrasing 'The source of an Aether YARA rule' is slightly indirect compared with a plain 'Returns the source of...' but costs little.

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 one-parameter read tool with no output schema, the description covers what is returned, how the parameter must match, and when to reach for it. The only meaningful gap is failure behavior for an unknown rule name, a minor omission at this complexity level.

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 already documents 'Exact rule name, e.g. from get_yara_matches.' The description reinforces the exactness requirement but adds no new syntax or format detail beyond the schema, which is the correct baseline here.

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?

Names the specific resource (an Aether YARA rule) and scopes the return contents to meta, strings and condition, retrieved by exact name. The distinction from get_yara_matches is implied by the reference to seeing a rule that came from there, though the verb is nominal ('the source of') rather than an explicit 'retrieve/return'.

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?

An explicit 'When to use' clause ties invocation to the user wanting to inspect a rule surfaced by get_yara_matches or understand what it looks for. Clear positive guidance and a named related tool, but no statement of when not to use it (e.g. for listing or searching rules by pattern).

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