Skip to main content
Glama

Recreation Gov

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.8/5.0
Behavior5/5

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

Adds crucial details beyond annotations: scoping by identifier, persistence differences for authenticated vs anonymous users. 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?

Well-structured with purpose first, then usage, then behavior. All sentences add value, though could be slightly condensed.

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 simplicity (two string params, no output schema), description fully covers purpose, usage, persistence, and pairing with other tools. No gaps.

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 both parameters fully; description adds illustrative examples for key and clarifies value as any text, enhancing practical understanding.

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?

Description uses specific verb 'Save' and resource 'data' with clear scope 'across sessions'. Differentiates from siblings 'recall' and 'forget' by stating pairing.

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?

Explicitly states when to use: 'discover something worth carrying forward'. Provides context like avoiding re-lookup and mentions alternatives 'recall' and 'forget'.

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