magicsword-mcp

Official

by magicsword-io

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Find MagicSword alerts

find_alerts

Read-onlyIdempotent

Search MagicSword alerts by severity, ack state, time window, hostname, or MITRE technique for triage queries; filters run server-side before pagination.

Instructions

Search MagicSword alerts by severity, ack state, time window, hostname, or MITRE technique. All filters run server-side before pagination, so total and page counts describe the actual result set. Use this for triage queries like "unack'd critical alerts in the last 24h".

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

Input Schema

Name	Required	Description
`limit`	No	Page size (default 50, max 200)
`since`	No	ISO8601 lower bound on created_at (e.g. "2026-05-08T00:00:00Z" or "2026-05-09")
`offset`	No	Skip this many records before returning
`hostname`	No	Glob matched case-insensitively against endpoint name, e.g. "prod-*"
`severity`	No	Restrict to one severity tier
`acknowledged`	No	true = only acked alerts, false = only unacked, omit = both
`mitre_technique`	No	Exact MITRE ATT&CK technique or sub-technique, e.g. "T1059" or "T1059.001"

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare the safe read-only, idempotent, non-destructive profile, so the bar is lowered. The description still adds genuine value by disclosing that filters run server-side before pagination, meaning total and page counts reflect the real result set — a behavioral trait not visible in the schema or annotations.

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?

Three tight sentences, all front-loaded: purpose first, then the pagination caveat, then the usage example. No filler; each sentence carries distinct information.

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?

With 7 optional params fully documented in the schema, safety covered by annotations, and pagination behavior explained, an agent has enough to call this correctly. No output schema is present, yet the description touches on result counts; the only minor gap is the absence of sibling routing guidance.

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%, so every parameter (limit, since, offset, hostname, severity, acknowledged, mitre_technique) is already documented in the schema. The description names those same dimensions but adds no extra format or syntax detail beyond what the schema provides, so baseline 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 specific verb ('Search') and resource ('MagicSword alerts') and enumerates the filterable dimensions (severity, ack state, time window, hostname, MITRE technique). It is clearly distinguishable from siblings like list_events or triage_alert, though it never explicitly names what it is not.

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?

Gives a concrete usage context: triage queries such as "unack'd critical alerts in the last 24h". This makes the intended use case clear, but no exclusions or explicit alternatives (e.g. when to prefer triage_alert) are provided.

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