Skip to main content
Glama

national-parks-mcp-server

by io.github.cyanheads

national-parks-mcp-server: find parks

nps_find_parks
Read-only

Resolve a place name, US state, or free-text query to National Park Service parks — the required first step before the detail tools. Returns each park's parkCode (the key nps_get_park, nps_get_alerts, nps_find_campgrounds, nps_get_activities, and nps_find_events all use) plus a compact trip-planning summary (designation, states, description, coordinates, headline activities, entrance fee, NPS page). Coverage is US NPS sites only — national parks, monuments, historic sites, seashores — not state parks and not Forest Service or BLM land.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum parks to return (1–50). The full set is ~470 sites; narrow with query/stateCode rather than paging through everything.
queryNoFree-text search across park names and descriptions (e.g. "yosemite", "civil war", "redwood"). Results are re-ranked locally so an exact parkCode or name match leads: NPS returns matches in alphabetical-by-code order with no relevance ranking, so without this the obvious park can sit behind sites that only mention the term in their description. Omit to browse by state. At least one of query or stateCode is recommended; with neither, returns the first page of all ~470 NPS sites.
startNoZero-based offset for pagination within the matched set. Use with limit to page through results.
activityNoFilter to parks offering an activity, matched against each park's activities list (e.g. "hiking", "camping", "stargazing"). Case-insensitive substring match applied locally (the API has no activity param) across every site matching query/stateCode, then paginated with start/limit — so totalCount is the true count of matching parks, not a per-page tally. Use nps_get_park to see a park's full activity list.
stateCodeNoTwo-letter US state/territory code, or comma-separated list (e.g. "CA", "WY,MT,ID"). Filters to parks located in those states. Combine with query to narrow.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNoThe limit applied to this response (populated when results were truncated).
errorNoPresent when the call failed. Absent on success.
parksNoMatching parks, each carrying the parkCode needed to chain into the detail tools.
shownNoNumber of parks returned in this response (populated when the result set was capped by limit).
noticeNoGuidance when no parks matched — suggests broadening the query, checking the state code, or dropping the activity filter.
totalCountNoTotal parks matching the query/state filter before the limit was applied.
appliedFiltersNoEcho of the filters as the server applied them (query / stateCode / activity), so the agent can see what was searched.

TDQS

A5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true and openWorldHint=true, which are generic. The description adds significant behavioral detail: local re-ranking for exact matches, that NPS returns results in alphabetical-by-code order with no relevance ranking, that the activity filter is a local substring match (the API has no activity param), and that totalCount reflects true matches across all parks. It also clarifies pagination semantics and coverage scope. These are exactly the behaviors an agent needs to interpret results correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is packed but efficient. The first sentence establishes purpose and the required-first-step role, then bullet-like details enumerate return contents, then a compact coverage clause. No wasted words; every sentence carries functional information. For an entry-point tool with five optional parameters, this length is justified and well-front-loaded.

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 the tool's complexity (5 optional params, no required, local filtering, re-ranking, ~470 sites) and the presence of an output schema, the description covers all critical usage scenarios: parameter combinations, edge cases (no query/stateCode), pagination behavior, and the relationship to detail tools. Nothing an agent needs to call this correctly is missing.

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

Parameters5/5

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

Schema coverage is 100%, so each parameter already has a description. The description goes further: it explains the re-ranking nuance for query, the local filtering and totalCount semantics for activity, and the pagination behavior for start/limit. It also warns against paging through all sites with limit and suggests narrowing with query/stateCode. This adds genuine 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?

States a specific verb ('Resolve') with a clear resource ('place name, US state, or free-text query to National Park Service parks') and immediately positions it as 'the required first step before the detail tools.' It lists exactly what is returned (parkCode, trip-planning summary) and explicitly names the sibling tools that depend on it, making differentiation trivial.

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 declares when to use this tool ('first step before the detail tools'), when to omit parameters ('Omit to browse by state'), and what happens with no parameters ('returns the first page of all ~470 NPS sites'). It also states exclusions ('not state parks and not Forest Service or BLM land') and recommends using at least one of query or stateCode. No ambiguity about usage context.

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