Rec-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_campgroundsC | Find camping facilities near a specified location. Searches for camping facilities within a customizable radius of a city using the Recreation Information Database (RIDB) API. First geocodes the city to get coordinates, then searches for campgrounds and camping facilities in the surrounding area. Returns a JSON string containing facility information including any available image URLs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'find_campgrounds' has a clear, distinct purpose focused on locating camping facilities near a specified location, leaving no room for confusion or misselection.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'find_campgrounds' follows a clear verb_noun pattern (find + campgrounds), which would be consistent if more tools were added, but as a standalone, it sets a good precedent without any deviations or mixed conventions.
A single tool is too few for a server named 'Rec-MCP', which suggests a broader recreation domain. While the tool is well-defined for finding campgrounds, the server lacks coverage for other recreation activities (e.g., hiking trails, parks, events), making it feel thin and incomplete for its apparent scope, leading to potential agent failures in broader tasks.
The tool surface is severely incomplete for a recreation domain. It only provides a 'find' operation for campgrounds, with no CRUD/lifecycle coverage (e.g., no create, update, delete, or get details for campgrounds or other recreation resources). This creates significant gaps that will hinder agents from performing comprehensive recreation-related tasks.