Skip to main content
Glama

Funcheap

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

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

Adds details beyond annotations: describes returned event structure, mark_read behavior, and feed location. No contradictions.

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?

Concise paragraph with front-loaded purpose, no wasted sentences. Could be more structured but effective.

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 covers return structure and key behaviors. Missing pagination details, but limit parameter addresses it.

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 coverage is 100%, and description adds examples and behavioral context for filter parameters beyond schema descriptions.

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 clearly states the tool pulls fired events from subscription feed, distinguishes from siblings like search_events by focusing on persisted feed.

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 and alternative HTTP access, but no explicit when-not-to-use. Still provides good context for usage.

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

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

A4.1/5.0
Disambiguation4/5

Most tools are distinct (event search, subscriptions, memory, Polymarket arbitrage, data lookups), but ai_visibility_check, scan_competitor_ai_presence, bet_research, polymarket_edges, and polymarket_arbitrage have overlapping purposes around competitive research and prediction-market edge-finding. The detailed descriptions disambiguate them, though an agent could confuse polymarket_edges with polymarket_arbitrage.

Naming Consistency4/5

Tool names are mostly descriptive and consistent: search_events, event, categories, tags are aligned; ask_pipeworx, compare_entities, entity_profile follow a similar pattern. However, polymarket_* tools have an odd mix of `polymarket_arbitrage`, `polymarket_fill_risk`, and `polymarket_edge_tracker`, and discover_tools/recent_alerts/recent_changes are consistent, mostly. Naming is quite consistent overall with minor deviations.

Tool Count3/5

At 35 tools, the count is heavier than typical MCP servers, but it reflects a broad service (Funcheap data + Pipeworx data platform + pred markets). Still, plenty of tools serve the same primary purpose (polymarket_, ask_pipeworx variants) so some pruning would improve the surface.

Completeness4/5

The surface appears complete for its domain: search/retrieve events, category/tag navigation, memory, subscriptions (create/list/cancel/pull), data lookups, entity resolution, comparisons, profiles, edge scanning, and feedback. Minor gaps include no direct 'update' on events (but events are static), and no pricing fetch tool separate from event text, though body text covers it.

Resources