Nps

List Parks

list_parks

Read-onlyIdempotent

List or search NPS parks. Filter by free-text query, state code (2-letter, comma-separated), or parkCode list. Returns full name, description, designation, states, GPS, address, official URL.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "Yellowstone"
    },
    "name": "list_parks"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Results (1-500, default 25)
`query`	No	Free-text search
`start`	No	0-based offset (default 0)
`state`	No	2-letter state code(s), comma-separated (e.g., "CA,NV")
`park_code`	No	Specific parkCode(s), comma-separated (e.g., "yose,grca")

Output Schema

Name	Required	Description
`parks`	Yes	List of parks
`total`	Yes	Total number of parks matching criteria
`returned`	Yes	Number of parks in this response

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "Yellowstone"
+  },
+  {
+    "limit": 50,
+    "state": "CA,NV"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "parks": {
+      "description": "List of parks",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Park description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "designation": {
+            "description": "Park designation (e.g., National Park)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "full_name": {
+            "description": "Full official name of park",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "latitude": {
+            "description": "Latitude coordinate",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "longitude": {
+            "description": "Longitude coordinate",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Short name of park",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "park_code": {
+            "description": "4-letter NPS park code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "states": {
+            "description": "State codes where park is located",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "Official NPS website URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of parks in this response",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of parks matching criteria",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "parks"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, etc. The description adds value by specifying the output fields (full name, description, designation, states, GPS, address, official URL) and filter options, offering context beyond the annotations without contradiction.

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, front-loaded with the core purpose, and every word adds information. It is efficient without redundancy.

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?

The description covers the main purpose, filters, and return fields. With an output schema present, it is sufficiently complete. Minimal gaps (e.g., pagination is not mentioned but start and limit parameters exist in schema) do not detract significantly.

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 parameter descriptions. The description reinforces the parameter usage (e.g., '2-letter, comma-separated' for state, 'parkCode list') and clarifies how filters can be combined, adding practical meaning 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?

The description clearly states 'List or search NPS parks' and specifies filtering options and return fields, distinguishing it from sibling tools like 'get_park' (single park) and other listing tools.

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 lists filtering options but does not explicitly guide when to use this tool versus alternatives like 'get_park' or other list tools. It implies usage for park listing/search but lacks explicit when-to-use or when-not-to-use guidance.

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

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.