PermitSnag

Search US campgrounds

search_campgrounds

Read-onlyIdempotent

Find campgrounds in the US by name, area or state, across Recreation.gov and state park booking systems. Use this when someone wants a place to camp or asks about a specific campground. Returns up to 10 campgrounds with their PermitSnag page, their booking system, and whether PermitSnag can send an alert when a site opens. It does not check dates; use check_availability for that.

Input Schema

Name	Required	Description
`limit`	No	How many results, 1 to 10. Default 5.
`query`	Yes	A campground name or area, like "Upper Pines" or "Big Sur".
`state`	No	Optional two-letter US state code to narrow results, like CA.

Output Schema

Name	Required	Description	Default
`query`	Yes
`state`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "description": "US campgrounds that match the search.",
+  "properties": {
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "bookingSystem": {
+            "type": "string"
+          },
+          "depth": {
+            "description": "site_level: our checks count individual sites. campground_level: the booking system reports the campground as a whole.",
+            "enum": [
+              "site_level",
+              "campground_level"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "pageUrl": {
+            "type": "string"
+          },
+          "scannable": {
+            "description": "True when PermitSnag checks this campground for openings. Whether an alert is on offer today is in get_campground_details.",
+            "type": "boolean"
+          },
+          "state": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "state",
+          "bookingSystem",
+          "depth",
+          "pageUrl",
+          "scannable"
+        ],
+        "type": "object"
+      },
+      "maxItems": 10,
+      "type": "array"
+    },
+    "state": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "query",
+    "state",
+    "results"
+  ],
+  "type": "object"
+}

First observedOct 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds meaningful non-annotation context: result cap (up to 10), which booking sources are queried, what each result carries, and that no date checking occurs. It stops short of detailing pagination or ranking behavior.

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?

Four sentences, front-loaded with purpose and scope, then use-case, then return shape, then the explicit exclusion. Every sentence carries distinct information with no filler.

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?

A read-only search tool with full schema coverage and an output schema; the description covers purpose, when-to-use, the sibling handoff, and source coverage. No information an agent needs to select or call it correctly is missing.

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 description coverage is 100%, so query, state and limit are already documented in the schema. The description reinforces that search works by name, area or state but adds no format or syntax detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource ('Find campgrounds in the US') plus scope ('across Recreation.gov and state park booking systems'), and names the search dimensions (name, area, state). It is clearly distinguishable from siblings like check_availability and get_campground_details.

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?

Explicitly states when to use it ('when someone wants a place to camp or asks about a specific campground') and when not to ('It does not check dates; use check_availability for that'), naming the alternative directly. Nothing is left to inference.

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

All PermitSnag 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.

Resources

Need Help?