Nps

List Things To Do

list_things_to_do

Read-onlyIdempotent

Activities recommended by the park service — hikes, ranger programs, scenic drives, ranger-led activities. Filter by parkCode or state.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	1-500 (default 25)
`query`	No	Free-text query (optional)
`state`	No	2-letter state code (optional)
`park_code`	No	parkCode (optional)

Output Schema

TableJSON Schema

Name	Required	Description
`total`	Yes	Total number of activities
`returned`	Yes	Number of activities in this response
`activities`	Yes	List of activities and things to do

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "park_code": "zion"
+  },
+  {
+    "query": "hiking",
+    "state": "WA"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "activities": {
+      "description": "List of activities and things to do",
+      "items": {
+        "properties": {
+          "activities": {
+            "description": "Activity types",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "duration": {
+            "description": "Duration of activity",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "fees_apply": {
+            "description": "Whether fees apply",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Activity ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "location": {
+            "description": "Activity location",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "park_code": {
+            "description": "Park code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "pets_permitted": {
+            "description": "Whether pets are permitted",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "reservation_required": {
+            "description": "Whether reservation is required",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "short_description": {
+            "description": "Short description of activity",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Activity title",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "topics": {
+            "description": "Related topics",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "url": {
+            "description": "Activity URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of activities in this response",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of activities",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "activities"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnly and idempotent hints. The description adds that the tool returns park service activities and filtering options, but does not add behavioral traits like pagination or rate limits beyond annotations.

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 two sentences: first clearly states purpose with examples, second explains filtering. No filler, front-loaded with key information.

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?

Given the simple parameter set and existence of output schema, the description is mostly complete. It could mention default behavior or pagination, but overall sufficient for a list tool.

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 coverage is 100% with each parameter described. The description mentions filtering by parkCode or state, which aligns with schema, but does not add new semantic meaning beyond what is already in 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?

The description clearly states the tool lists activities recommended by the park service, with specific examples like hikes and ranger programs. It distinguishes from sibling tools like list_parks and list_alerts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions filtering by parkCode or state, implying when to use, but does not explicitly state when not to use or name alternatives among sibling tools.

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

All Nps tools Inspect

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.