Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does reasonably well: it discloses the return shape (source, citation_uri, raw event payload), the persistence model, and the state-mutating side effect of mark_read:true. It omits auth requirements, rate limits, and what happens to events already read, which keeps it from a 5.

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?

Four tight sentences, front-loaded with purpose, then filters, then the state-changing option, then an escape hatch for scripts. No filler, and the most decision-relevant details (mark_read side effect) appear before the incidental HTTP endpoint note.

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 no output schema, the description correctly fills that gap by describing returned fields, and it covers filtering, polling strategy, and the read-state side effect for a read-and-mutate hybrid tool. Missing auth and rate-limit context for a polling endpoint slightly reduces completeness.

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 the baseline is 3. The description adds a useful example value for type ('sec_8k') and explains the downstream consequence of mark_read (subsequent calls show only newer events), slightly beyond the schema's 'Flag the returned events read in the same call.' However, limit, since, and unread_only receive no description-level elaboration.

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?

The description opens with a specific verb and resource: 'Pull fired events from your subscription feed,' and clarifies the scope as alerts the evaluator wrote to the persisted feed. It also enumerates what each returned event contains (source, citation_uri, raw payload), so the agent knows exactly what it gets. It does not explicitly differentiate itself from siblings like recent_changes or list_subscriptions, keeping it 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?

It gives concrete operational guidance: 'Polls work fine' and 'Set mark_read:true ... so the next call only shows newer ones,' which tells the agent how to use the tool for incremental polling. It also names a non-MCP alternative (the raw JSON endpoint) for scripts and dashboards. It stops short of stating when other MCP siblings should be used instead.

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.