Skip to main content
Glama

Nps

by io.github.pipeworx-io

List Campgrounds

list_campgrounds
Read-onlyIdempotent

Campgrounds inside a park or state. Returns name, description, RV/tent capacity, amenities, reservation info, GPS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo1-500 (default 25)
queryNoFree-text query (optional)
stateNo2-letter state code (optional)
park_codeNoparkCode (optional)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal number of campgrounds
returnedYesNumber of campgrounds in this response
campgroundsYesList of campgrounds

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"
+  },
+  {
+    "limit": 100,
+    "state": "UT"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "campgrounds": {
+      "description": "List of campgrounds",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Campground description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "fees": {
+            "description": "Camping fees",
+            "items": {
+              "properties": {
+                "cost": {
+                  "description": "Fee cost",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "title": {
+                  "description": "Fee type title",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "group_sites": {
+            "description": "Number of group sites",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Campground ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "latitude": {
+            "description": "Latitude coordinate",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "longitude": {
+            "description": "Longitude coordinate",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Campground name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "park_code": {
+            "description": "Park code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "reservation_info": {
+            "description": "Reservation information",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "rv_sites": {
+            "description": "Number of RV sites",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "tent_only": {
+            "description": "Number of tent-only sites",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "total_sites": {
+            "description": "Total number of campsites",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "Campground URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "walk_or_boat_to": {
+            "description": "Walk or boat to sites count",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "wheelchair_access": {
+            "description": "Wheelchair accessibility info",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of campgrounds in this response",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of campgrounds",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "campgrounds"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds that it returns specific fields, but does not elaborate on pagination, result limits, or any side effects. With annotations covering safety, this is adequate.

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

Conciseness4/5

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

Two short sentences that are front-loaded and efficient. Could be slightly more structured (e.g., separating purpose from return fields), but no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and parameters are fully covered, the description is minimally complete. It lists return fields but doesn't mention available filters (park_code, state, limit, query) or that results are a list. Adequate but not rich.

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 descriptions for all four parameters. The description does not add meaning beyond the schema (e.g., clarifying typical usage of 'query' vs 'state'). Baseline score of 3 applies as schema already documents parameters.

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 campgrounds within a park or state, and enumerates the return fields (name, description, capacity, amenities, etc.). It distinguishes from siblings like 'list_parks' by specifying the resource and filter scope.

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?

No explicit guidance on when to use this tool versus alternatives like 'list_parks' or 'search_within'. The context implies filtering by park or state, but lacks 'when not to use' or mentions of sibling tools for different needs.

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