Skip to main content
Glama

National park entrance conditions this week

get_park_conditions
Read-onlyIdempotent

Use when someone is planning a visit to a U.S. national park. Returns this week's official facts for a ParkReady-covered park (optionally one entrance): open/closed entrances and roads, NPS alerts and closures, an NWS forecast snapshot, seasonal hazards with what to do, and a prep checklist, each with NPS/NWS source links. Accepts a name ('Zion'), NPS code ('yose') or slug. If the park is not covered it says so and gives the official NPS conditions URL; never fill gaps with guesses.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "park": "<park>"
    },
    "name": "get_park_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
parkYesPark name, NPS park code or slug, e.g. 'Yosemite' or 'grca'
entranceNoOptional entrance name or slug, e.g. 'South Entrance'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a safe read, but the description adds substantive behavior: data is official and this week's (freshness), every fact carries an NPS/NWS source link (provenance), uncovered parks degrade to an official URL, and 'never fill gaps with guesses' sets an explicit no-hallucination contract. That is real disclosure beyond readOnlyHint/idempotentHint.

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?

Front-loaded with the usage trigger, then the payload, then identifier formats, then the fallback — a logical order with no filler sentences. The middle sentence is a long comma-separated list, slightly dense, but each clause carries information an agent needs.

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?

There is no output schema, so the description carries the return-value burden and does so thoroughly by naming each section of the response plus the source-link behavior. Combined with the uncovered-park case and single-entrance option, nothing an agent needs to call or interpret this 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 coverage is 100% and the parameter descriptions already state name / NPS code / slug with examples and the optional entrance. The description restates the accepted identifier forms ('Zion', 'yose', slug) and optional single entrance without adding new syntax or validation rules, so the schema is doing the work — 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?

Names a specific verb and resource — 'Returns this week's official facts for a ParkReady-covered park' — and enumerates the payload (entrance/road status, NPS alerts, NWS forecast snapshot, seasonal hazards, prep checklist). An agent can distinguish it from the neighboring weather tool because the forecast is only one of several bundled sections.

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?

'Use when someone is planning a visit to a U.S. national park' gives an explicit usage trigger, and the uncovered-park fallback ('it says so and gives the official NPS conditions URL') defines the boundary condition. It stops short of naming an alternative sibling such as get_nws_forecast_and_alerts for pure weather questions, so it is clear context but not full when/when-not routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources