Skip to main content
Glama

Nyt

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).

TDQS

B3.3/5.0
Behavior1/5

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

The description discusses a 'mark_read' parameter that flags events as read, implying state mutation. However, annotations declare 'readOnlyHint: true', indicating no side effects. This is a direct contradiction, reducing transparency and potentially misleading the AI agent.

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?

The description is concise, consisting of three clear sentences. It front-loads the purpose, then details key parameters and behavior, and ends with an alternative access method. No superfluous information; every sentence adds value.

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?

Given the tool has 5 optional parameters and no output schema, the description covers the main functionality, returned fields, filtering, and mark_read behavior. It also mentions polling suitability and a REST alternative. However, it omits details on 'limit' and 'unread_only' parameters, which are only in the schema. Still largely complete.

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 adds value by explaining how to use 'type' with an example ('sec_8k'), describing 'since' as an ISO timestamp, and clarifying the behavior of 'mark_read' (flags events read, affects future calls). 'limit' and 'unread_only' are not elaborated, but overall parameter understanding is enhanced.

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 clearly states it pulls fired events from a subscription feed, specifying the resource (subscription feed) and action (pull/return). It mentions returning specific fields and filtering options. However, it does not explicitly distinguish from sibling tools like 'list_subscriptions', which list subscriptions themselves, but the context of 'alerts' and 'events' provides adequate differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving recent alerts from a persisted feed, with filtering and mark-read functionality. It mentions polling and an alternative REST endpoint, but does not explicitly state when to use this tool versus siblings or when not to use it. Guidance is present but not comprehensive.

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

All Nyt 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
Disambiguation2/5

ask_pipeworx and ask_pipeworx_beta are explicitly identical today, and ask_pipeworx_grounded, deep_research, and validate_claim all route to the same underlying sources with overlapping question-answering purposes. Entity-focused tools like entity_profile, compare_entities, recent_changes, and resolve_entity also have fuzzy boundaries that make selection error-prone.

Naming Consistency2/5

Names mix conventions: verb_noun (list_subscriptions, search_articles, generate_llms_txt), bare verbs (remember, recall, forget), noun phrases (polymarket_arbitrage, pipeworx_trending, entity_profile), and an ask_* family with beta/grounded variants. There is no consistent verb or noun pattern across the set.

Tool Count2/5

With 35 tools, the surface is well above the 15-tool threshold for a focused server, and most tools are unrelated to the NYT domain implied by the server name. The breadth reflects a broad data-platform grab bag rather than a scoped, intentional tool set.

Completeness4/5

The query side is unusually complete: single-lookup, grounded lookup, deep research, claim validation, entity resolution, comparison, profile, change-feed, discovery, memory, and subscription lifecycle tools are all present. Minor gaps remain, such as no direct NYT article fetch by URL and no update path for stored memories, but agents can work around them.

Resources