Skip to main content
Glama

Nps

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

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.

Input Schema

TableJSON 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. Dates show when Glama detected each change.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. Description adds important behavioral detail: the mark_read parameter flags events as read, affecting subsequent calls, and explains polling suitability. This extends beyond 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?

Concise, well-structured: opens with purpose, details return fields, explains parameters, describes side effects, and notes alternative access. Every sentence adds unique value with no redundancy.

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?

Despite no output schema, the description explains return fields (source, citation_uri, raw payload) and covers main use cases (filtering, mark_read). Lacks pagination detail for limit but is otherwise comprehensive for a read tool with strong annotations.

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

Parameters5/5

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

Schema coverage is 100%, but description adds rich context: explains 'type' filters by subscription type, 'since' uses ISO timestamps with fired_at semantics, 'mark_read' and 'unread_only' have clear behavioral effects, and 'limit' defaults to 50. Greatly enhances 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?

Description clearly states the tool pulls fired events from a subscription feed and returns the most recent alerts. It specifies return fields and distinguishes from siblings like list_alerts by focusing on the persisted feed and mark_read functionality.

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?

Explicitly says polls work fine and points to an alternative GET endpoint for scripts/dashboards, giving context on when to use this tool vs. direct access. Lacks explicit when-not guidance but is clear enough.

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

All Nps toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Most tools have clearly distinct purposes (e.g., NPS park tools vs. Pipeworx queries vs. Polymarket analysis). Some overlap exists between ask_pipeworx and ask_pipeworx_grounded, and among the many Polymarket tools, but descriptions help differentiate them.

Naming Consistency3/5

Naming conventions vary: some use verb_noun (list_parks), others use descriptive phrases (ask_pipeworx_grounded, scan_competitor_ai_presence). While all use snake_case, there is no consistent pattern in prefixes or verb choice.

Tool Count2/5

35 tools is too many for a coherent server. The set appears to bundle multiple unrelated domains (NPS, Pipeworx, Polymarket, memory, subscriptions) into a single server, lacking focused scope.

Completeness3/5

Each domain has notable gaps (e.g., NPS lacks real-time conditions; Pipeworx lacks data ingestion tools; Polymarket lacks order placement). Some sub-areas (memory, subscriptions) are complete, but overall the surface is incomplete for the broad range of domains.

Resources