Skip to main content
Glama

Data Denver

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds behavioral details: returns specific fields (source, citation_uri, payload), mark_read flag behavior, and polling suitability. No contradictions; adds value beyond annotations.

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?

Single paragraph, well-structured with purpose first. Each sentence contributes value. Could be slightly more concise but remains clear and informative.

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 explains return fields. Parameters all documented. For a read-only list tool with good annotations, it covers essential behavior (polling, alternative endpoint, usage). Missing explicit pagination details but limit parameter covers it.

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%, so baseline is 3. Description explains 'type' with example 'sec_8k', 'since' as ISO timestamp, and 'mark_read' behavior. However, 'unread_only' is not mentioned in description but is in schema. Adds some meaning but not exhaustive.

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 it pulls fired events from the subscription feed, specifying the resource (alerts) and action (pull/return). Distinguishes itself from siblings like subscribe or list_subscriptions by focusing on the alert feed content. Uses specific verb 'Pull' and identifies return fields.

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?

Description provides explicit usage context: 'Polls work fine' and mentions an alternative access method via a REST endpoint for scripts/dashboards. Lacks explicit when-not-to-use or comparison to other tools, but context is sufficient for most cases.

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

All Data Denver 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/5.0
Disambiguation3/5

Tools are richly described with clear use-cases, but several clusters overlap: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded/deep_research are all question-routing tools with similar names, and the five polymarket_* tools cover adjacent prediction-market analysis. An agent could easily pick the wrong one without reading the full descriptions.

Naming Consistency4/5

All names are snake_case and mostly follow a verb_noun or domain_noun pattern (compare_entities, resolve_entity, denver_query, polymarket_edges, pipeworx_trending). There are minor deviations like single verbs (remember, forget), adjective-first names (recent_alerts, deep_research), and domain-prefixed groups, but the overall style is predictable and readable.

Tool Count2/5

34 tools is a large surface for one server, pushing beyond the 25+ threshold where agents struggle to choose. While the platform is genuinely multi-domain (data lookup, prediction markets, Denver open data, memory, subscriptions, npm checks, llms.txt generation), several niche clusters like the 5-tool Polymarket suite and 3-tool memory trio inflate the count.

Completeness4/5

The server covers its domain well: general querying, grounded verification, deep research, entity resolution, company profiling, change feeds, subscription lifecycle (subscribe/list/unsubscribe/alerts), memory lifecycle (remember/recall/forget), and discovery (discover_tools, suggest_questions). Minor gaps exist—such as no direct browsing of all Pipeworx sources—but agents can work around them.

Resources