Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__recent_alerts

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed, each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

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": "ntsb-investigations__recent_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional, filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp, return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it describes the returned payload fields, discloses the state-changing side effect of mark_read (returned events get flagged read, changing future results), and states that polling is supported. It omits any auth/permission requirement and any rate-limit or retention behavior around the persisted feed.

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?

Front-loaded with the core action, then return shape, then filtering, then stateful semantics, then the script-access alternative. Every sentence contributes new information; there is no restatement of the tool name or filler.

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?

There is no output schema, and the description compensates by describing the per-event payload (source, citation_uri, raw payload). For a five-parameter, zero-required read tool this is largely sufficient; the main gaps are authentication requirements and whether the feed is per-account or shared.

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%, so the schema already documents all five parameters and the baseline is 3. The description adds modest value with an example enum-like value for type ("sec_8k"), the ISO format for since, and the downstream consequence of mark_read — but limit, unread_only, and ordering are left entirely to the 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?

"Pull fired events from your subscription feed" names a specific verb (pull/read) and a specific resource (the persisted subscription feed of fired events), and immediately clarifies what a returned item contains: source, citation_uri, and raw event payload. This makes it distinguishable from subscription-management siblings such as list_subscriptions without opening either schema.

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 concrete operating guidance: "Polls work fine", and it explains how to chain calls via mark_read:true so the next call only returns newer events. It also notes the same feed is reachable over HTTP for scripts and dashboards. It stops short of explicitly contrasting with alternatives (e.g. when to prefer this feed over recent_changes), so it is not a full when/when-not statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.