Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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.3/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 well: it discloses the read-plus-state-change nature of mark_read, that the feed is persisted server-side, and the shape of each returned event (source, citation_uri with pipeworx:// fallback, raw payload). It omits auth requirements, rate limits, and what an empty feed looks like, leaving some behavioral gaps.

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?

Four front-loaded sentences with no filler: purpose first, then return shape, then filtering, then the state-change flag, then the polling/HTTP alternative. The HTTP endpoint sentence is arguably tangential to tool invocation but is short and genuinely useful; nothing is redundant.

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 five-parameter read tool with no annotations and no output schema, the description covers the essentials: what the feed is, what each event carries, how filtering and read-flagging behave across calls. Missing only edge-case behavior such as empty results, ordering guarantees, or pagination beyond limit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description still adds meaning by giving a concrete type example ("sec_8k"), confirming since takes an ISO timestamp and compares against fired_at, and explaining the cross-call consequence of mark_read. The limit and unread_only parameters 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?

The first sentence names a specific verb and resource ("Pull fired events from your subscription feed") and immediately clarifies that the source is the evaluator's persisted feed rather than a live upstream API. That scope statement, plus the mention of per-event fields (source, citation_uri, raw payload), tells an agent exactly what this tool yields and how it differs from a generic per-provider alerts tool.

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 clear operational context: polling is supported, mark_read:true makes the next call incremental, and a raw HTTP endpoint exists for scripts/dashboards. It does not state when to prefer this over a sibling alerts tool or any prerequisites/auth, so it stops short of full when/when-not guidance.

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.