Skip to main content
Glama

Unicef

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

A3.7/5.0
Behavior2/5

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

The description discloses that setting mark_read:true flags events as read, which is a state-modifying action. However, annotations declare readOnlyHint: true, creating a contradiction. The description should either align with annotations or explain the state change.

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?

The description is a single paragraph of ~80 words, front-loaded with the purpose. It is information-dense but could be more structured with bullet points for parameters. Still within acceptable conciseness.

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?

The description covers what is returned, filtering options, mark_read behavior, and an alternative access method. It is complete for a list-like tool, but the contradiction with annotations reduces completeness slightly.

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 coverage is 100% with descriptions for all 5 parameters. The description adds context like filtering by type (e.g., 'sec_8k') and explains the effect of mark_read, but this largely mirrors the schema. Baseline score is appropriate.

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 the tool 'Pull fired events from your subscription feed' and specifies it returns recent alerts with source, citation_uri, and raw event payload. This leaves no ambiguity about the tool's core function.

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 mentions that polling works fine and provides an alternative URL for scripts/dashboards, offering some usage context. However, it does not explicitly differentiate from sibling tools like list_subscriptions or explain when to prefer this tool.

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

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

Several tool families heavily overlap: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve 'find/query Pipeworx data' with blurry boundaries, and the six Polymarket tools (bet_research, polymarket_edges, polymarket_edge_tracker, polymarket_arbitrage, polymarket_fill_risk, polymarket_kalshi_spread) have overlapping purposes. An agent could easily pick the wrong one without reading every description.

Naming Consistency3/5

Most tools follow snake_case verb_noun patterns (list_dataflows, get_data, compare_entities, resolve_entity), and families share prefixes (pipeworx_*, polymarket_*, ask_pipeworx_*). However, the server is named 'Unicef' while almost all tool names reference Pipeworx/Polymarket, and verb choices vary widely, so the overall set lacks a unified naming story.

Tool Count1/5

34 tools is already on the high side, but the real problem is scope: only 3 tools (list_dataflows, dataflow_structure, get_data) relate to the server's stated UNICEF purpose, while the other 31 are an unrelated grab bag of Pipeworx research, prediction-market betting, memory utilities, npm scanning, and llms.txt generation. This is a severe mismatch between count and purpose.

Completeness2/5

For the UNICEF domain implied by the server name, the surface is minimal: browse, structure, and fetch data cover read-only access but nothing else, and the overwhelming majority of tools are off-domain. If the inferred domain is instead 'Pipeworx + prediction markets', coverage is broad, but then the server name is fundamentally misleading and the UNICEF subset is an incomplete afterthought.

Resources