Skip to main content
Glama

Stocktwits

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.6/5.0
Behavior4/5

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

Description adds context beyond annotations: scoped by identifier, 24-hour retention for anonymous sessions. Annotations indicate idempotent and non-destructive, which description aligns with.

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?

Three sentences front-loaded with main purpose, then usage guidance, then technical detail. No wasted words.

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?

Covers purpose, usage, parameter semantics, and pairing with recall/forget. Minor gap: no mention of return value or confirmation behavior, but schema and annotations suffice.

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 has 100% coverage with descriptions for key and value. Description enhances by suggesting naming conventions and content types (findings, addresses, preferences).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses specific verb 'save' and resource 'data' with clear scope 'to reuse later'. It distinguishes from sibling tools by explicitly naming recall and forget.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'when you discover something worth carrying forward'. Provides examples and notes persistence differences for authenticated vs anonymous users.

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