Skip to main content
Glama

Unicode

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

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

Beyond annotations (readOnlyHint, idempotentHint, openWorldHint), the description adds crucial details: each event carries source and citation_uri, mark_read behavior flags events so next call shows newer, and polling works fine. 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?

Four sentences, each earning its place: main action, return structure, filter options, side effects and alternatives. No fluff, front-loaded with purpose.

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?

Given 5 optional params with full schema coverage and no output schema, the description compensates by explaining return structure. Annotations provide safety profile. Missing error handling or authentication details, but adequate for typical use.

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% with parameter descriptions. The description adds meaning by explaining mark_read's effect (flag read to show newer events) and mentions limit implicitly. It does not cover unread_only explicitly, but schema already describes it.

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 pulls fired events from the subscription feed, distinguishing it from sibling tools like list_subscriptions which list subscription types. The verb 'Pull' and resource 'fired events' are specific.

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 explains filtering by type and since, setting mark_read, and mentions polling suitability. It also provides an alternative endpoint for scripts/dashboards. However, it does not explicitly state when not to use this tool versus alternatives like search tools.

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

All Unicode 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.8/5.0
Disambiguation3/5

Several tools overlap significantly: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded serve nearly the same routing purpose, with the beta variant currently identical to the stable one, and deep_research also overlaps for broad research. However, most other tools have clearly distinct functions, and descriptions provide usage guidance, so ambiguity is moderate.

Naming Consistency3/5

Most names are snake_case and readable, but patterns vary between verb_noun (compare_entities, resolve_entity), noun phrases (entity_profile, polymarket_edges), and bare verbs (remember, subscribe). The pipeworx_ and polymarket_ prefixes are used inconsistently across the set, and the server name 'Unicode' does not align with the tool names.

Tool Count2/5

At 34 tools, the server is overloaded for a focused purpose, especially since only three tools relate to Unicode despite the server name. Many Polymarket and Pipeworx tools could be consolidated, and the count exceeds the well-scoped range of 3-15 tools, making the set feel bloated and unfocused.

Completeness2/5

The server name claims to be about Unicode, but only char_info, escape_string, and unescape_string cover that domain, missing common operations like normalization, case conversion, and encoding validation. For the broader data-access domain the surface is fairly complete, yet there is no tool to fetch a specific pipeworx:// citation URI, leaving cited records unfetchable within the tool set—an obvious gap relative to the stated capabilities.

Resources