Skip to main content
Glama

Serper

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?

The description states that setting mark_read:true flags events as read, which is a write operation. However, annotations include readOnlyHint: true, indicating no state modification. This contradiction makes the description misleading.

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?

The description is three sentences, front-loaded with purpose, and each sentence adds value—no 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?

Given no output schema, the description explains return fields (source, citation_uri, payload), filtering, mark_read side effect, and polling suitability. It is complete for a simple read tool.

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 each parameter. The description adds usage context for type, since, and mark_read, e.g., 'set mark_read:true to flag returned events read' which is above the baseline.

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 uses specific verb 'Pull' and resource 'fired events from your subscription feed', clearly stating what the tool does. It distinguishes from siblings by focusing on alerts and mentioning the alternative endpoint for scripts.

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 implies usage for polling ('Polls work fine') and points to an alternative REST endpoint, but does not explicitly state when not to use this tool or contrast with its many sibling tools.

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

All Serper 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
Disambiguation3/5

The ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) has blurry boundaries — ask_pipeworx_beta is explicitly identical to ask_pipeworx today — and the six Polymarket tools (polymarket_arbitrage, polymarket_edges, polymarket_fill_risk, etc.) all operate in the opportunity-detection space. Extremely detailed descriptions help, but an agent could easily select the wrong variant.

Naming Consistency3/5

Snake_case is used throughout and the polymarket_* and pipeworx_* clusters are internally consistent, but the set mixes verb-first names (ask_pipeworx, resolve_entity, validate_claim) with noun-first names (entity_profile, recent_changes, news, places) roughly evenly. The 'beta' suffix on a stable production tool and the adjective-noun 'deep_research' add further inconsistency.

Tool Count2/5

At 34 tools this exceeds the 25+ threshold, and the count is padded with redundancy: three near-identical ask_pipeworx variants, ai_visibility_check wrapped by scan_competitor_ai_presence, and six overlapping Polymarket tools. The unusually broad multi-domain scope justifies more tools than a typical server, but several clusters could be consolidated.

Completeness4/5

The surface is thorough for a read-only data-access gateway: universal routing, grounded verification, entity resolution/profiles/comparisons, web/news/maps search, prediction-market analysis, memory CRUD, and a full subscription lifecycle. Minor gaps exist (no direct fetch tool for pipeworx:// citation URIs, no image/video Serper endpoints) but agents can work around them.

Resources