Skip to main content
Glama

Recreation Gov

by io.github.pipeworx-io

Entity Profile

entity_profile
Read-onlyIdempotent

"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO, news, GLEIF and returns: cik + company_name; recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (LATEST 10-K Revenues + NetIncomeLoss + Cash, sorted period_end DESC); patents (USPTO PatentsView API sunset May 2025 — soft-fails until reactivated); recent news mentions via GDELT→GNews fallback; LEI via GLEIF. Pass ticker "AAPL" or zero-padded CIK "0000320193" — names not supported (use resolve_entity first if you only have a name).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today; person/place coming soon.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193"). Names not supported — use resolve_entity first if you only have a name.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds rich behavioral context: fans out across multiple sources (SEC, XBRL, USPTO, news, GLEIF), lists return fields, and discloses a limitation (patents soft-fail due to sunset). No contradictions 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?

The description is fairly long but well-structured, front-loaded with example queries and key guidance. Every sentence adds value (use cases, instructions, limitations). Could be slightly trimmed without losing information, but overall efficient.

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?

No output schema, but the description provides a comprehensive list of return fields (cik, company_name, recent_filings, fundamentals, patents, news, LEI) with sources and ordering. It covers limitations (patents soft-fail) and expected behavior, making it complete for an agent to invoke and interpret results.

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%, so baseline is 3. Description adds value beyond schema: explains that 'value' accepts ticker or CIK, explicitly says names not supported, and clarifies 'type' is only 'company'. This extra context helps agents use parameters correctly.

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 explicitly states the tool's purpose: 'full cross-source profile of a US public company in ONE parallel call.' It provides concrete example queries ('Tell me about X', 'research Acme') and distinguishes from siblings by instructing to prefer this over chaining single-pack lookups. Unique among siblings (e.g., compare_entities, search_within), ensuring no confusion.

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?

Clear guidance on when to use (holistic company view) and when not to (names not supported; use resolve_entity first). Explicitly says 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' Also specifies input format (ticker or CIK) and requirement to resolve names first, covering alternatives.

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