Skip to main content
Glama

national-parks-mcp-server

by io.github.cyanheads

national-parks-mcp-server: find campgrounds

nps_find_campgrounds
Read-only

Campgrounds at a park or across a state: amenities (potable water, showers, RV dump station, toilets, trash collection, RV access), reservable vs. first-come-first-served site counts, reservation guidance and booking URL, accessibility, and fees — answering "where can I camp at Zion, and can I get an RV hookup?" Get park codes from nps_find_parks. Some parks list lodging or backcountry permits instead of NPS-managed campgrounds; an empty result is not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum campgrounds to return (1–50).
queryNoFree-text search across campground names/descriptions (e.g. "river", "group", "rv").
startNoZero-based pagination offset.
parkCodeNoPark code, or comma-separated list (e.g. "zion") — 4-letter lowercase codes. Get codes from nps_find_parks. Provide parkCode or stateCode.
stateCodeNoTwo-letter state code, or comma-separated list. Returns campgrounds across all NPS sites in those states.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNoLimit applied (populated when results were truncated).
errorNoPresent when the call failed. Absent on success.
shownNoCampgrounds returned in this response (populated when capped by limit).
noticeNoGuidance when no campgrounds matched.
totalCountNoTotal campgrounds matching the filter before the limit was applied.
campgroundsNoCampgrounds at the requested park(s)/state(s).
appliedFiltersNoEcho of parkCode/stateCode/query as applied.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly and openWorld. Description adds caveat about empty results not being an error, which clarifies behavior beyond annotations. No contradictions. Does not discuss rate limits or pagination, but schema covers start/limit.

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?

Two sentences covering purpose, content, and a caveat. Front-loaded with action and output type. No filler, but the example question adds slight verbosity without major cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive for a query tool: describes return fields, dependency on park codes, edge case of empty results. Output schema exists, so return structure is further specified. Missing explicit pagination behavior but schema provides start/limit fields.

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

Parameters3/5

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

Schema description coverage is 100%, so parameters are already documented. Description adds example use of query ('river', 'group', 'rv') and reminds to get park codes from another tool, but does not deepen semantic meaning beyond schema. Meets baseline for high coverage.

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?

Clear verb+resource: 'find campgrounds'. States exact fields returned (amenities, site counts, fees) and answers a concrete user question ('where can I camp at Zion, and can I get an RV hookup?'). Distinct from siblings like events or alerts; references nps_find_parks as prerequisite.

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?

Describes context of use (campground search) and explicitly points to nps_find_parks for codes. Warns that some parks return lodging/backcountry permits instead, so empty results expected. Does not name alternative tools to switch to, but the dependency is clear.

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

All national-parks-mcp-server 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

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct domain resource: parks, park details, alerts, events, activities, and campgrounds. There is no overlap in purpose; an agent can unambiguously select the right tool for a query.

Naming Consistency5/5

All tools follow a consistent `nps_` prefix with a verb-noun pattern (`find_*` or `get_*`). The only minor variation is singular/plural nouns, but this is predictable and does not hinder understanding.

Tool Count5/5

Six tools is well-scoped for a national parks API, each covering a core aspect of trip planning (lookup, detail, alerts, events, activities, campgrounds). No tool feels redundant or unnecessary.

Completeness4/5

The surface covers primary trip-planning needs: finding parks, getting detailed info, checking alerts, seeing events, exploring activities, and finding campgrounds. Minor gaps like webcams or permits are non-essential, but the set is nearly complete.

Resources