Skip to main content
Glama

Timeapi Io

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

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

Annotations declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds the behavior of mark_read (flagging events as read) and confirms polling is fine, providing useful context beyond annotations. 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?

The description is a single paragraph of 3-4 sentences, front-loaded with purpose. It is efficient with no wasted words, though a more structured format (e.g., bullet points) could improve readability.

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 parameters, no output schema, and comprehensive annotations, the description covers behavior, parameters, and alternative access (GET endpoint). Minor gaps: no mention of error handling or rate limits.

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 descriptions for all 5 parameters. The description adds meaningful context, e.g., explaining that mark_read:true causes next calls to show only newer events, going beyond the schema's basic description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it pulls fired events from a subscription feed and lists what each alert carries (source, citation_uri, raw payload). It does not explicitly differentiate from sibling tools like list_subscriptions, but the purpose is specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions polling works and the same feed is available via GET, but does not provide explicit guidance on when to use this tool vs alternatives. Usage context is implied but not directly stated.

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

All Timeapi Io 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

B3.2/5.0
Disambiguation2/5

Several tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer natural-language data questions, and ask_pipeworx_beta is explicitly identical to ask_pipeworx right now. The current_time* variants and multiple Polymarket scanners also create real selection ambiguity, though the memory and subscription tools are clearly distinct.

Naming Consistency3/5

Names are mostly lowercase snake_case and readable, but there is no consistent verb_noun pattern: some are imperative (ask_pipeworx, compare_entities, generate_llms_txt) while others are object-first (entity_profile, recent_changes, pipeworx_trending). Subfamilies like current_time* and polymarket_* are internally consistent, but the overall set follows no predictable convention.

Tool Count2/5

Forty tools is far too many for a server named Timeapi Io; only about nine tools actually relate to time zones and current time. The rest form a sprawling Pipeworx research, prediction-market, memory, and subscription platform, making this a mega-bundle rather than a well-scoped toolset.

Completeness3/5

The time-related surface covers current time, zone conversion, zone metadata, and ISO parsing, but lacks common date math or general formatting operations. The Pipeworx side is quite complete for research and fact-checking, but the mixed domain makes coverage uneven and hard to reason about as a single coherent service.

Resources