Skip to main content
Glama

Stocktwits

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint as true/true/true/false. The description adds that mark_read:true flags events as read so next call shows only newer ones, a behavioral side-effect. It doesn't contradict annotations or introduce negative traits.

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 four sentences, front-loaded with purpose and key details. Every sentence adds value: purpose, return fields, filtering, mark_read behavior, and alternative endpoint. No wasted words.

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?

Given the tool is read-only with no output schema, the description sufficiently explains return values and mark_read effect. It also addresses polling suitability and provides an alternative REST endpoint, covering practical usage concerns.

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 all 5 parameters (100% coverage). The description adds examples (type 'sec_8k', ISO timestamp for since) and explains mark_read effect, enhancing understanding beyond the raw schema descriptions.

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 subscription feed, specifying return fields (source, citation_uri, payload). It is specific about resource and action, but does not explicitly distinguish from siblings like `list_subscriptions` or `subscribe`, leaving some ambiguity.

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 explains how to use the tool: filter by type and/or since, set mark_read. It mentions an alternative REST endpoint for scripts/dashboards and states polls work fine, providing context. However, it does not explicitly state when not to use this tool versus alternatives.

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

All Stocktwits 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.5/5.0
Disambiguation2/5

Multiple tools serve overlapping functions: three ask_pipeworx variants, two deep research tools, and multiple polymarket tools. StockTwits-specific tools are distinct but the overall set has significant ambiguity between Pipeworx and Polymarket tools.

Naming Consistency2/5

Naming styles are mixed: some use lowercase (ask_pipeworx), some use underscores (ai_visibility_check), and some use prefixes (pipeworx_feedback, polymarket_arbitrage). No consistent pattern across the tool set.

Tool Count3/5

40 tools is on the higher end but not extreme. However, many tools belong to the Pipeworx ecosystem, which seems separate from StockTwits, making the set feel bloated and unfocused for a single server.

Completeness2/5

StockTwits social features are adequately covered (symbol search, streams, trending), but the inclusion of Pipeworx tools creates a sprawling surface without complete coverage in any one domain. Missing core StockTwits features like user profiles or direct messaging.

Resources