Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses that the feed is persisted, that returned events carry source, citation_uri and raw payload, and — critically — that mark_read mutates server-side read state, a side effect an agent must know before calling. It omits auth requirements, rate limits, and ordering guarantees.

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?

Six short sentences, front-loaded with what the tool returns before moving to filtering and the read-flag workflow. Nothing is redundant, though the trailing HTTP-endpoint sentence is a convenience note rather than essential selection guidance.

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, so the description must describe returns, and it does name the meaningful fields of each event. For a zero-required-parameter polling tool it is nearly complete; only ordering, pagination behavior past limit, and auth prerequisites are left unaddressed.

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 by giving a concrete type example ('sec_8k') and by explaining the downstream effect of mark_read, but says nothing about limit or unread_only interaction.

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 concrete verb+resource phrase ('Pull fired events from your subscription feed') and elaborates that these are alerts the evaluator wrote to a persisted feed, which is far more specific than the tool name alone. It never names or contrasts with likely-adjacent siblings such as recent_changes or list_subscriptions, so an agent must infer the boundary from context.

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 real operating guidance: 'Polls work fine' legitimizes repeated calls, and 'Set mark_read:true ... so the next call only shows newer ones' explains the cursor-style workflow for incremental consumption. It stops short of stating when to prefer a different tool or when this one is inappropriate, and gives no guidance on choosing between mark_read and unread_only.

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.