Skip to main content
Glama

Census Trade

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 indicate read-only, idempotent, non-destructive behavior. Description adds value by detailing return fields (source, citation_uri, raw payload) and the mark_read flag's effect on future calls. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five sentences, no filler. Front-loaded with action and resource, then covers returns, filtering, mark_read, and alternative access. Every sentence adds value.

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?

With no output schema, description adequately describes return fields and behavior. Covers filtering, mark_read, polling suitability, and alternative access. Complete for the tool's complexity.

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?

Input schema has 100% description coverage. Description adds context beyond schema, e.g., explaining mark_read 'so the next call only shows newer ones' and providing an example type 'sec_8k'. Slightly above 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?

The description clearly states the tool retrieves recent alerts from a subscription feed, using a specific verb ('Pull') and resource ('fired events from your subscription feed'). Distinguishes from sibling tools like list_subscriptions, which list subscriptions, not alerts.

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 that polling is fine and provides an alternative API endpoint for scripts/dashboards, but does not explicitly address when to avoid this tool or compare to similar sibling tools. Provides guidance on mark_read and unread_only usage.

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

All Census Trade 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
Disambiguation2/5

There is substantial overlap among the question-routing tools: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, and ask_pipeworx_grounded, deep_research, and validate_claim all funnel natural-language queries into similar source lookups. ai_visibility_check and scan_competitor_ai_presence also cover nearly the same capability, making tool selection genuinely ambiguous.

Naming Consistency3/5

All names are snake_case and many follow a verb_noun pattern (census_exports, list_subscriptions, validate_claim), but the convention drifts with noun-first names like entity_profile, pipeworx_trending, and recent_alerts, and bare verbs like remember, recall, forget, and subscribe. It is readable but not a tight, predictable pattern.

Tool Count2/5

35 tools is too many for a server named 'Census Trade' when only 4 of them actually relate to Census trade data. The remaining 31 form an unrelated general-purpose data, prediction-market, memory, and subscription toolkit, making the surface feel bloated and badly scoped relative to the server's apparent purpose.

Completeness3/5

The Census trade core covers exports, imports, trade balance, and monthly trends, which handles the central queries, but there is no HS-code catalog, country metadata, or state/port-level breakdown, leaving notable gaps for a trade-data domain. If judged as the broad Pipeworx gateway it appears to actually be, coverage is richer, but that contradicts the server name and weakens overall coherence.

Resources