Skip to main content
Glama

climate

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.9/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true, but the description explicitly describes mark_read:true as flagging events read, which mutates state. This directly contradicts the read-only hint, lowering the score to 1.

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?

Two dense sentences with no filler; every clause adds functional information (return fields, filtering, mark_read, polling, alternative endpoint).

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?

Description covers return value structure (source, citation_uri, raw payload), filtering, read-flag side effect, polling suitability, and HTTP mirror, making it self-sufficient without an output schema.

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 already covers all 5 parameters, but the description adds behavioral nuance for mark_read (only newer events on next call) and clarifies type/since usage, exceeding schema info.

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 opens with 'Pull fired events from your subscription feed' and further clarifies it returns recent alerts with payload details, distinguishing it from subscription management tools like subscribe/unsubscribe.

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?

It advises polling works fine and directs scripts/dashboards to an HTTP endpoint, providing clear context for interactive use vs automation. However, it doesn't explicitly name alternative MCP tools, so it's not a perfect 5.

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

All climate 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.9/5.0
Disambiguation2/5

Multiple query-router tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and bet_research all serve as entry points into the same underlying data, with ask_pipeworx_beta explicitly described as currently identical to ask_pipeworx. Prediction-market tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk) also have fuzzy boundaries that an agent could easily mis-select.

Naming Consistency3/5

Most tools follow a readable lower_snake_case verb_noun pattern (compare_entities, get_climate_projection, resolve_entity), but conventions are mixed: pipeworx_feedback, pipeworx_trending, recent_alerts, and recent_changes are noun-first/non-imperative, and the ask_pipeworx family uses a verb-plus-variant-suffix style. The pattern is predictable enough to navigate but not consistent.

Tool Count2/5

33 tools is heavy for a single MCP server, and the server name 'climate' does not match the broad data-research, prediction-market, memory, subscription, and web-utility scope actually covered. Several tools could be consolidated (ask_pipeworx variants, discover_tools/suggest_questions, multiple polymarket scanners), which would reduce cognitive load without losing capability.

Completeness4/5

As a general data-access and research surface, the tool set is quite complete: it covers lookup, grounded verification, deep research, entity resolution, comparisons, recent changes, memory, subscriptions, alerts, feedback, and tool discovery. Minor gaps exist — the climate-specific coverage is limited to projections and model comparison despite the server name, and there is no direct tool to page through the full catalog — but for its inferred broad purpose there are no major dead ends.

Resources