national-parks-mcp-server

national-parks-mcp-server: get activities

nps_get_activities

Read-only

Curated things to do and points of interest at a park — title, description, time commitment, location, accessibility, and fee/pet/reservation flags — answering "what should I do at Acadia?" Covers the NPS editorially-curated activity list (distinct from a park's raw activity tags in nps_get_park). Accepts a single 4-letter park code or a single two-letter state code, and at least one is required. Not every park has a curated list; an empty result is not an error.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum activities to return (1–50).
`query`	No	Free-text search across activity titles/descriptions (e.g. "sunrise", "hike", "tour").
`start`	No	Zero-based pagination offset.
`parkCode`	No	A single 4-letter lowercase park code (e.g. "acad"). Get it from nps_find_parks. Accepts one park code, not a list. Provide parkCode or stateCode.
`stateCode`	No	A single two-letter state code (e.g. "ME"). Returns curated activities across NPS sites in that state.

Output Schema

TableJSON Schema

Name	Required	Description
`cap`	No	Limit applied (populated when results were truncated).
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Activities returned in this response (populated when capped by limit).
`notice`	No	Guidance on the result set: where else to look when no curated activities matched, the start value for the next page when more matched, or the way back when start ran past the end.
`truncated`	No	True when more activities matched than this response returned; absent on a complete result.
`activities`	No	Curated activities and points of interest for the requested park/state.
`totalCount`	No	Total activities matching the filter before the limit was applied.
`appliedFilters`	No	Echo of parkCode/stateCode/query as applied.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 24, 2026

removedInput schema / properties / parkCode / pattern
```
Removed value: -"^[a-z]{4}$"
```
removedInput schema / properties / stateCode / pattern
```
Removed value: -"^[A-Za-z]{2}$"
```

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `missing_filter`: Neither parkCode nor stateCode provided. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `missing_filter`: Neither parkCode nor stateCode provided. `invalid_park_code`: parkCode isn't a single 4-letter lowercase code. `invalid_state_code`: stateCode isn't a single two-letter code. Other values are possible when a failure originates below the handler."

changedOutput schema / properties / error / properties / data / properties / reason / examples

Previous value: -[
-  "missing_filter"
-]New value: +[
+  "missing_filter",
+  "invalid_park_code",
+  "invalid_state_code"
+]

changedOutput schema / properties / notice / description

Previous value: -"Guidance when no curated activities matched."New value: +"Guidance on the result set: where else to look when no curated activities matched, the start value for the next page when more matched, or the way back when start ran past the end."

addedOutput schema / properties / truncated

Added value: +{
+  "description": "True when more activities matched than this response returned; absent on a complete result.",
+  "type": "boolean"
+}

Changed16 schema fields changedSep 20, 2026
- removedOutput schema / properties / activities / items / properties / accessibility / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / activities / items / properties / accessibility / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / activities / items / properties / duration / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / activities / items / properties / duration / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / activities / items / properties / feeDescription / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / activities / items / properties / feeDescription / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / activities / items / properties / latitude / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / activities / items / properties / latitude / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / activities / items / properties / location / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / activities / items / properties / location / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / activities / items / properties / longitude / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / activities / items / properties / longitude / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / activities / items / properties / parkCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / activities / items / properties / parkCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / activities / items / properties / url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / activities / items / properties / url / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed6 schema fields changedAug 24, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "activities",
+      "totalCount",
+      "appliedFilters"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `missing_filter`: Neither parkCode nor stateCode provided. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "missing_filter"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "activities",
-  "totalCount",
-  "appliedFilters"
-]

First observedJun 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already provide readOnlyHint and openWorldHint, but the description adds substantial behavioral context beyond those: it clarifies that only a single code is accepted (not a list), that at least one code is required despite the schema having no required fields, and that an empty result is normal for parks without curated lists. It also notes the source of the park code (nps_find_parks). These details are not implied by the annotations and materially help correct invocation.

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 with essential information in a compact, front-loaded format. It opens with the return type and fields, then states the use case, the distinction from a sibling, input constraints, and an edge case—all in a few sentences with zero filler. Every sentence earns its place.

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 has an output schema (so return format is already documented), the description covers everything an agent needs: what the tool returns, how to filter (park or state), the single-code constraint, the requirement for at least one code, and the empty-result behavior. No essential behavioral or selection information is missing.

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% with per-parameter descriptions, so baseline is 3. The description adds value by explaining that parkCode must be a single lowercase 4-letter code sourced from nps_find_parks, that stateCode is two-letter and returns activities across sites, and that at least one of the two is required. This goes beyond the schema's individual field descriptions, though it does not fully detail every param (e.g., limit/start are left to 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?

The description clearly identifies the tool as returning curated activities for a park or state, listing the specific fields (title, description, time commitment, etc.) and the exact use case ('what should I do at Acadia?'). It explicitly distinguishes itself from nps_get_park's raw activity tags, which is a direct sibling differentiator.

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?

It provides explicit when-to-use context (answering activity recommendations) and a clear exclusion: 'distinct from a park's raw activity tags in nps_get_park'. It also states the accepted inputs (single park code or state code) and that at least one is required, plus the edge case that empty results are not an error. This fully guides an agent on when and how to invoke it.

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.