Skip to main content
Glama

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.

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": "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. Changed2 schema fields changed
    • changedInput schema / properties / since / description
      Previous value: -"Optional ISO timestamp — return events fired_at >= this time."New value: +"Optional ISO timestamp, return events fired_at >= this time."
    • changedInput schema / properties / type / description
      Previous value: -"Optional — filter to one subscription type."New value: +"Optional, filter to one subscription type."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description adds real behavior beyond the annotations: the return shape (source, citation_uri with the pipeworx:// scheme, raw event payload), the fact that events persist in a feed the evaluator writes to, and critically that mark_read:true changes feed state so subsequent calls return fewer events. That last point matters because readOnlyHint:true might otherwise lead an agent to assume a pure read; the description surfaces the caveat rather than hiding it.

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 sentences, front-loaded with what it returns, then filtering, then the side-effect flag, then the alternative access path. Little waste; the HTTP endpoint sentence is arguably tangential for an MCP-calling agent but is short and informative.

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?

No output schema exists, so the description carries the burden of describing returns, and it does so (source, citation_uri, raw payload). It also covers persistence, polling, and the read-state side effect. The gap is that it never mentions the limit parameter or unread_only, though the schema documents both.

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 the baseline is 3. The description still earns a bump by giving a concrete type example ('sec_8k'), restating that since is an ISO timestamp, and explaining the interaction semantics of mark_read — that flagged events drop out of later results. It leaves limit and unread_only entirely to the schema, which is acceptable given the coverage.

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 that these are 'the most recent alerts the evaluator has written to your persisted feed'. That's concrete enough to know it's a read of a personal alert feed. It doesn't explicitly distinguish itself from the sibling 'recent_changes', which is the most likely confusion point.

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?

Usage context is present but indirect: it notes 'Polls work fine', explains that mark_read makes 'the next call only shows newer ones', and points at an HTTP alternative for scripts and dashboards. What's missing is explicit when-to-use guidance versus sibling tools such as list_subscriptions or recent_changes — the agent has to infer that this reads a feed while those do other things.

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.