Skip to main content
Glama

Quotable

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by detailing the return fields (source, citation_uri, raw payload) and the behavior of mark_read (flags returned events as read), which is beyond what annotations provide. No contradictions 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?

The description is concise, with no wasted words. It front-loads the primary purpose, then details parameters and usage. Each sentence contributes meaningfully, achieving high density of information without verbosity.

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 no output schema, the description explicitly states what each alert carries. It covers all parameters, usage patterns, and even an alternative API. For a read-only, idempotent tool with comprehensive annotations, this description is fully adequate.

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 description coverage is 100%, so the baseline is 3. The description adds meaning by clarifying that 'type' filters by subscription type, 'since' is an ISO timestamp, and 'mark_read' flags events as read. This goes beyond repeating schema definitions, providing actionable context.

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?

The description clearly states it pulls fired events from the subscription feed and returns the most recent alerts. It specifies the resource (alerts) and the action (pull/return), distinguishing it from sibling tools by focusing on alert retrieval. The verb 'Pull' and resource 'fired events' are specific and unambiguous.

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 explicit guidance on filtering by type and since, using mark_read, and notes that polling works fine. It also mentions an alternative endpoint for scripts/dashboards. While it doesn't explicitly state when not to use this tool, the context is sufficient for an AI agent to decide.

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

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

The ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) is highly overlapping—two of them are explicitly identical right now—and the six polymarket_* tools plus bet_research create unclear boundaries between prediction-market analysis tools. Company-focused tools (entity_profile, compare_entities, recent_changes, resolve_entity) also partially overlap in what they fetch, making tool selection error-prone.

Naming Consistency4/5

Most tool names follow a clear snake_case pattern with descriptive verbs (search_quotes, resolve_entity, validate_claim, subscribe, unsubscribe). There is good use of family prefixes like polymarket_* and pipeworx_*, though the Pipeworx family mixes prefix and suffix placement (ask_pipeworx vs. pipeworx_feedback), which is a minor inconsistency.

Tool Count2/5

35 tools is far too many for a server named 'Quotable', especially since only 4 tools (get_authors, list_tags, random_quote, search_quotes) relate to quotes. The rest span data lookup, prediction markets, memory, subscriptions, AI visibility, and dependency scanning—an extremely broad, unfocused scope that overwhelms the apparent purpose.

Completeness3/5

The quote-related surface is minimal but functional (random, search, authors, tags), though missing obvious operations like get_quote_by_id. The data-lookup and prediction-market domains are thoroughly covered with grounding, research, arbitrage, and fill-risk tools, so the broader set is complete—but it does not serve the server's stated identity as a quotes provider.

Resources