Skip to main content
Glama

airports

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 provide readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral detail: each event carries source, citation_uri, and raw payload; mark_read flags events; feed is persisted; and the same feed is available via HTTP. No contradiction 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, front-loaded with the core purpose, and each sentence delivers unique, non-redundant information. No filler or wasted words.

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, the description adequately covers return payload details, filtering options, mark_read semantics, and the alternative HTTP access point. It is complete for a read-only tool with well-documented parameters and annotations.

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% and each parameter is described. The description supplements with a concrete filter example ('sec_8k'), clarifies mark_read side effects, and explains the returned event structure, adding value beyond the schema.

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 function: 'Pull fired events from your subscription feed' and 'Returns the most recent alerts the evaluator has written to your persisted feed'. This specific verb+resource distinguishes it from sibling tools like list_subscriptions and recent_changes.

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 provides clear usage context: filtering by type and since, polling behavior, and the alternative HTTP endpoint for scripts. It does not explicitly name sibling alternatives or exclusions, but the practical guidance is sufficient.

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

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

Many tools have distinct purposes, but the three 'ask_pipeworx' variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) are highly similar and likely cause confusion. Additionally, the toolset mixes airport-specific tools with unrelated financial and research tools, creating ambiguity about when to use which.

Naming Consistency2/5

Naming conventions are inconsistent: some tools use descriptive snake_case (ai_visibility_check, ask_pipeworx), others are single verbs (remember, forget, recall), and some include brand names (pipeworx_feedback). No clear pattern emerges across the 34 tools.

Tool Count1/5

34 tools is excessive for a server named 'airports'—only 3 tools directly relate to airports (search_airports, get_airport, calculate_distance). The majority are unrelated utilities (financial, prediction markets, memory), making the scope far too broad and unfocused.

Completeness1/5

The server severely lacks completeness for its stated airport domain: there are no tools for flights, airlines, runways, or real-time data. The other included domains (e.g., financial, prediction markets) are also incomplete, with e.g., only partial coverage of company data and no update/delete operations.

Resources