Skip to main content
Glama

Grants Gov

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.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 returned events as read, which is a mutable side effect. This directly contradicts the annotation readOnlyHint=true, indicating a serious inconsistency. The description should align 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?

The description is two paragraphs: the first covers purpose and return fields, the second covers parameters with examples. Every sentence adds value, and there is no verbosity. It is efficiently structured.

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?

Despite lacking an output schema, the description explains return fields (source, citation_uri, raw payload) and mentions pagination via limit and mark_read. It covers all parameters and provides an alternative endpoint for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant value by explaining mark_read behavior, giving concrete filter examples (e.g., 'sec_8k'), clarifying limit range (1-200, default 50), and describing the effect of unread_only. This meaningfully extends 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 tool 'Pull fired events from your subscription feed' and specifies that it returns recent alerts with key fields (source, citation_uri, raw payload). This distinguishes it from siblings like list_subscriptions or search_opportunities, which serve different purposes.

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 guidance on when to use (polls work fine) and mentions an alternative endpoint for scripts/dashboards. However, it lacks explicit scenarios for when not to use or direct comparisons to sibling tools.

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

All Grants Gov 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.6/5.0
Disambiguation2/5

Many tools have overlapping purposes: ask_pipeworx/ask_pipeworx_grounded/deep_research all handle broad queries; multiple Polymarket tools exist for edge finding; entity_profile/compare_entities/recent_changes/resolve_entity overlap on company data. An agent would struggle to pick the right tool.

Naming Consistency2/5

Naming patterns are mixed: some use verb_noun (search_opportunities, get_opportunity), some are phrases (ask_pipeworx_grounded, polymarket_edge_tracker), and some are vague (recall, forget). No consistent convention across the set.

Tool Count2/5

32 tools is high, but the core issue is that the server name 'Grants Gov' implies a narrow focus, yet only 2 tools are about grants. The sheer number of unrelated tools makes the set feel bloated and unfocused.

Completeness3/5

For the actual domain of general data querying and prediction markets, the tool surface is fairly complete, covering many sources. However, for 'Grants Gov' it is severely incomplete (missing all but opportunities). Overall, the scope is broad but lacks depth in any one area.

Resources