Skip to main content
Glama

Nps

by io.github.pipeworx-io

Get Park

get_park
Read-onlyIdempotent

Fetch a single park by parkCode. Returns full description, designation, activities, topics, address, contacts, operating hours, entrance fees, and image gallery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
park_codeYes4-letter NPS parkCode (e.g., "yose", "grca", "yell")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoOfficial NPS website URL
nameYesShort name of park
imagesNoPark images
statesNoState codes where park is located
topicsNoTopics related to the park
latitudeNoLatitude coordinate
addressesNoPhysical addresses
full_nameYesFull official name of park
longitudeNoLongitude coordinate
park_codeYes4-letter NPS park code
activitiesNoActivities available in the park
descriptionYesDetailed park description
designationNoPark designation
weather_infoNoWeather information for the park
entrance_feesNoEntrance fee information
directions_infoNoDirections and access information
operating_hoursNoOperating hours information

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "park_code": "yell"
+  },
+  {
+    "park_code": "yose"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "activities": {
+      "description": "Activities available in the park",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "addresses": {
+      "description": "Physical addresses",
+      "items": {
+        "properties": {
+          "city": {
+            "description": "City",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "line1": {
+            "description": "Address line 1",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "postalCode": {
+            "description": "Postal code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "stateCode": {
+            "description": "State code",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "description": {
+      "description": "Detailed park description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "designation": {
+      "description": "Park designation",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "directions_info": {
+      "description": "Directions and access information",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "entrance_fees": {
+      "description": "Entrance fee information",
+      "items": {
+        "properties": {
+          "cost": {
+            "description": "Fee cost",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Fee description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Fee type title",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "full_name": {
+      "description": "Full official name of park",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "images": {
+      "description": "Park images",
+      "items": {
+        "properties": {
+          "alt": {
+            "description": "Alt text for accessibility",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Image title",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "Image URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "latitude": {
+      "description": "Latitude coordinate",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "longitude": {
+      "description": "Longitude coordinate",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Short name of park",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "operating_hours": {
+      "description": "Operating hours information",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Description of operating hours",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Name of operating hours entry",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "park_code": {
+      "description": "4-letter NPS park code",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "states": {
+      "description": "State codes where park is located",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "topics": {
+      "description": "Topics related to the park",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "url": {
+      "description": "Official NPS website URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "weather_info": {
+      "description": "Weather information for the park",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "park_code",
+    "full_name",
+    "name",
+    "description"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations indicate read-only, open-world, and idempotent behavior. The description adds detail on the rich response (full description, activities, fees, etc.), going beyond the 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 a single, well-structured sentence that conveys the tool's action and return value without unnecessary words.

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?

For a simple fetch-by-ID tool, the description covers the action, input, and output sufficiently. An output schema likely exists, so no further detail is needed.

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 a clear description of park_code parameter. The tool description does not add extra parameter semantics but provides context about the expected return, justifying a baseline 3.

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 'Fetch a single park by parkCode' and lists the data fields returned, distinguishing it from siblings like 'list_parks' which retrieves multiple parks.

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?

The description specifies the tool is for fetching a single park by code, implying when to use it. It does not explicitly exclude cases, but the requirement of a park_code clarifies the primary use case.

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

All Nps 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

A3.6/5.0
Disambiguation4/5

Most tools have clearly distinct purposes (e.g., NPS park tools vs. Pipeworx queries vs. Polymarket analysis). Some overlap exists between ask_pipeworx and ask_pipeworx_grounded, and among the many Polymarket tools, but descriptions help differentiate them.

Naming Consistency3/5

Naming conventions vary: some use verb_noun (list_parks), others use descriptive phrases (ask_pipeworx_grounded, scan_competitor_ai_presence). While all use snake_case, there is no consistent pattern in prefixes or verb choice.

Tool Count2/5

35 tools is too many for a coherent server. The set appears to bundle multiple unrelated domains (NPS, Pipeworx, Polymarket, memory, subscriptions) into a single server, lacking focused scope.

Completeness3/5

Each domain has notable gaps (e.g., NPS lacks real-time conditions; Pipeworx lacks data ingestion tools; Polymarket lacks order placement). Some sub-areas (memory, subscriptions) are complete, but overall the surface is incomplete for the broad range of domains.

Resources