Skip to main content
Glama

Base64

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

A3.5/5.0
Behavior1/5

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

Description implies that mark_read:true modifies state (flags events read), contradicting the readOnlyHint annotation which indicates no state changes. This is a direct contradiction, so score is 1.

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?

Description is a single paragraph, efficiently conveying purpose, filters, and extra context. Could be more structured, but not overly verbose.

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?

No output schema, but description specifies returned fields (source, citation_uri, raw event payload). Covers filtering and mark_read behavior. Adequate for a read tool with good annotations, but missing explicit return format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 5 parameters with descriptions. Description adds minor context (e.g., mark_read effect on subsequent calls) but does not significantly enhance beyond schema, maintaining baseline 3.

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?

Clearly states it pulls fired events from subscription feed, returns recent alerts with specific fields, and describes filtering options. Distinguishes itself from sibling tools like list_subscriptions.

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?

Mentions polling works fine and points to an alternative HTTP endpoint for scripts/dashboards. Provides context for when to use, but lacks explicit when-not or exclusion criteria.

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

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

Several tool groups have unclear boundaries: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, polymarket_edges / polymarket_arbitrage / polymarket_edge_tracker / polymarket_fill_risk / polymarket_kalshi_spread / bet_research all push prediction-market opportunities and can be confused, and ai_visibility_check is nested inside scan_competitor_ai_presence. discover_tools and suggest_questions also overlap as tool-discovery entry points.

Naming Consistency3/5

Everything is snake_case and mostly descriptive, but conventions are mixed: verb-first names (resolve_entity, validate_claim, compare_entities, search_within) sit beside noun-first names (entity_profile, recent_changes, bet_research, polymarket_edges), and brand-prefixed tools (pipeworx_feedback, pipeworx_trending) have unprefixed functional siblings (list_subscriptions, recent_alerts). The two actual Base64 tools (base64_encode, base64_decode) don't match the dominant Pipeworx naming style at all.

Tool Count2/5

33 tools is heavy for any single server, and the mismatch is extreme: the server is named 'Base64' yet only 2 of 33 tools relate to encoding/decoding — the other 31 form a sprawling data-research platform. Even judged as a data platform, the count exceeds the comfortable range and includes near-duplicates (the ask_pipeworx family, the Polymarket family).

Completeness4/5

The factual-data surface is well covered: query, grounded lookup, deep research, entity profiling, comparison, claim verification, entity resolution, subscriptions (subscribe/list/unsubscribe/recent_alerts), memory (remember/recall/forget), feedback, and tool discovery all exist with no obvious dead ends. The Base64 encoding domain is also complete (encode/decode across four variants). Minor gaps exist (e.g., no way to update a profile or edit memory entries) but they're workable.

Resources