Skip to main content
Glama

Lobsters

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.2/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, non-destructive. Description adds behavioral detail: mark_read:true flags events as read, affecting next call's results. No contradiction with 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?

Four concise sentences with front-loaded purpose. Every sentence provides essential information: purpose, return fields, filter options, mark_read effect, and alternative endpoint. No redundancy.

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

Completeness5/5

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

Despite lacking an output schema, the description details return fields (source, citation_uri, payload) and parameter usage. Covers all necessary context for a tool with simple inputs and outputs. Alternative endpoint adds completeness.

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 covers 100% of parameters with descriptions. Description adds value by explaining filter usage (example 'sec_8k', ISO timestamp) and clarifying mark_read behavior. Enhances understanding beyond schema.

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?

Description clearly states 'Pull fired events from your subscription feed' and specifies key return fields (source, citation_uri, raw payload). While it doesn't explicitly differentiate from sibling tools like 'list_subscriptions', the context of 'recent alerts' is specific enough to avoid confusion.

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?

Provides explicit guidance: 'Polls work fine' and suggests an alternative HTTP endpoint for scripts/dashboards. Does not contrast usage with sibling tools, but the alternative endpoint is a clear when-to-use hint.

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

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

Many tools have overlapping purposes, e.g., three tools for querying Pipeworx data (ask_pipeworx, ask_pipeworx_grounded, deep_research), and six tools for Polymarket prediction markets. The boundaries between them are unclear, causing potential for misselection.

Naming Consistency3/5

Tool names are all snake_case but follow inconsistent patterns: some use verb_noun (get_hottest, get_newest), some are single verbs (remember, forget), and others are noun_noun (bet_research, polymarket_arbitrage). While readable, the lack of a consistent pattern adds confusion.

Tool Count2/5

With 34 tools, the server is overloaded, especially given its name 'Lobsters' suggests a focus on that site, yet only 4 tools are Lobsters-related. The majority belong to Pipeworx, Polymarket, and generic utilities, making the scope extremely broad and unfocused.

Completeness2/5

For the implied domain of Lobsters, the tool set is incomplete (missing create/update/delete). For the broader domains (Pipeworx, Polymarket), the set is extensive but doesn't align with the server's name. The lack of a coherent domain leaves obvious gaps relative to any single purpose.

Resources