Skip to main content
Glama
Sign In

Nps

by io.github.pipeworx-io
OverviewDiscussionsAdmin

List Alerts

list_alerts
Read-onlyIdempotent

Current park alerts — closures, road conditions, weather warnings, danger advisories. Filter by parkCode or state.

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": {
      "park_code": "grca"
    },
    "name": "list_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-500 (default 50)
queryNoFree-text alert search
stateNo2-letter state code
park_codeNoparkCode(s), comma-separated

Output Schema

NameRequiredDescriptionDefault
totalYesTotal number of alerts
alertsYesList of current park alerts
returnedYesNumber of alerts in this response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "park_code": "grca"
+  },
+  {
+    "query": "closure",
+    "state": "CO"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "alerts": {
+      "description": "List of current park alerts",
+      "items": {
+        "properties": {
+          "category": {
+            "description": "Alert category",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Alert description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Alert ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "last_indexed": {
+            "description": "Last indexed timestamp",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "park_code": {
+            "description": "Park code for this alert",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Alert title",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "Alert URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of alerts in this response",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of alerts",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "alerts"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate safe, read-only behavior. The description adds context that alerts are 'current' and lists types, enhancing transparency. No contradictions with 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?

Single sentence conveys purpose, content, and filtering. No superfluous words; front-loaded with key information.

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?

Output schema exists, so return structure is covered. Description covers the tool's scope and filtering adequately for a simple list operation.

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 descriptive parameter documentation. The description reiterates filtering by parkCode or state but adds no new semantic detail 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 the tool lists current park alerts with specific categories (closures, road conditions, weather warnings, danger advisories) and mentions filtering by parkCode or state. This distinguishes it from sibling tools like list_parks or list_campgrounds.

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 indicates filtering options but lacks explicit guidance on when to use this tool vs alternatives like recent_alerts. No 'when not to use' or exclusion conditions are provided.

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