Skip to main content
Glama

Recreation Gov

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

TDQS

A4.8/5.0
Behavior5/5

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

Description adds significant behavioral detail beyond annotations (readOnlyHint, idempotentHint, destructiveHint): fans out to multiple sources, fallback mechanism (GDELT→GNews), soft-fail for USPTO, returns structured changes with citation URIs. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is detailed but well-structured, front-loaded with example queries. Every sentence adds value, though slightly verbose. Could be slightly more concise but overall effective.

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, description fully explains return structure (changes grouped by source, total_changes, citation URIs). Covers error/fallback behavior and the 'parallel call' nature. Complete for a change-feed tool with complex behavior.

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 covers 100% of parameters with descriptions. Description adds extra context: `since` accepts relative shorthand ("7d", "30d", "3m", "1y") and example usage, and clarifies `type` only supports 'company'. This adds 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 tool provides a change feed for a company in a given time window, listing specific sources (SEC EDGAR, GDELT/GNews, USPTO). It distinguishes itself from the sibling tool entity_profile by explicitly stating when to use which.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit example queries are given ("What's new with X", "latest on Y") and direct comparison to entity_profile: 'Use entity_profile instead when you want the static profile'. Provides clear when-to-use and when-not-to-use guidance.

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

All Recreation 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

B3.4/5.0
Disambiguation2/5

Many tools cluster around the same purpose: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all route questions to similar data sources, and the polymarket_* family has several overlapping edge/arbitrage scanners. The four Recreation.gov tools are distinct but are buried among unrelated Pipeworx tools, making selection ambiguous.

Naming Consistency3/5

Names are all snake_case and readable, with recognizable prefix families like ask_pipeworx*, polymarket_*, and pipeworx_* plus verb_noun names like search_facilities and list_campsites. However, the conventions are mixed: bare verbs, brand prefixes, and composite names coexist, and nothing in the naming signals that this is a Recreation.gov server.

Tool Count1/5

This server is named Recreation Gov but only 4 of 35 tools relate to recreation facilities; the other 31 are a general-purpose data, research, and prediction-market platform. That is an extreme scope mismatch for the server's stated purpose.

Completeness2/5

For the Recreation.gov surface, basic search and detail retrieval exist, but key operations like campsite availability, reservations, and permits are missing. The dominant Pipeworx functionality is unrelated to Recreation.gov, so the tool set as a whole has no coherent domain coverage.

Resources