Skip to main content
Glama

Septa

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. First observed

TDQS

B3.3/5.0
Behavior1/5

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

There is a contradiction: annotations set readOnlyHint=true, indicating no system state modification, but the description states that setting mark_read:true flags returned events as read, which is a state change. This directly contradicts the annotation, scoring 1 per instructions.

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?

The description is a single paragraph, efficient with no wasted words. The main purpose is front-loaded. Mention of the raw URL is slightly extraneous but not damaging.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so description should compensate. It mentions return fields (source, citation_uri, payload) but lacks full structure details, error cases, or examples. It is adequate but not comprehensive for a 5-parameter tool.

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%, baseline 3. The description adds context beyond schema descriptions by explaining the purpose of mark_read (flag events as read) and the filtering parameters. It integrates the parameters into a usage narrative, adding value.

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 the tool pulls fired events from the subscription feed, specifying the resource and action. It mentions key return fields like source, citation_uri, and payload. However, it does not explicitly differentiate from sibling tools like 'recent_changes', making it slightly less than a 5.

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?

The description provides clear context on filtering by type and since, and explains the mark_read flag usage. It also mentions polling suitability and an alternative raw URL. However, it lacks explicit 'when not to use' guidance or comparison with sibling tools, preventing a top score.

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

All Septa 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

A4.1/5.0
Disambiguation4/5

Most tools have distinct purposes, but there is some overlap among the ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and among the Polymarket tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread). However, detailed descriptions help differentiate them.

Naming Consistency3/5

Tool names mix conventions: snake_case is predominant, but there is no consistent verb_noun pattern. Some tools have 'septa_' prefix, but the majority do not follow a predictable structure. Naming is inconsistent across the set, though subgroups have some consistency.

Tool Count3/5

With 36 tools, the count is high. The server name 'Septa' suggests a focused transit server, but the tool set covers transit, data access, and prediction markets, making it overly broad. The number is borderline appropriate for a general-purpose server but misaligned with the name.

Completeness4/5

The transit domain is well-covered with alerts, positions, schedules, and train views. The data access and prediction market tools also cover their domains comprehensively. Minor gaps exist (e.g., no dedicated weather tool), but overall the tool set provides a wide range of capabilities.

Resources