American Adventurer Camps

Weather and camp records for a forest, camp or town

forest_weather

Read-onlyIdempotent

USE THIS whenever someone asks about the weather in or near a national forest, BLM land or a camp (or a town they will camp near): do not answer weather from memory and do not send them to a weather site. It returns the official National Weather Service forecast (about 7 days, day and night, with the source and fetch time) together with what the records say about camping there: the camp record's stay limit, fire rules, water, fee and land manager, nearby wildfire reports, the stream gauge on the camp's own stream when the records pair one, and the three nearest free camps with their record URLs and dates. Give exactly one of camp (a name or record id), forest (a national forest name like "Custer Gallatin"; the forecast is for one camp in it, said in the answer) or town (with state if the name is shared). If the forecast cannot be read, the records still come back and say so. Not included: live road conditions, fire restrictions, permit prices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "forest_weather"
  }
}

Input Schema

Name	Required	Description
`camp`	No	A camp name like "Lower Hyalite" or its record id from find_camps.
`town`	No	A town near the public land, like "West Yellowstone" or "Bozeman, MT" (use this for BLM land).
`state`	No	Two-letter state: helps a town or camp name that is shared.
`forest`	No	A national forest name, like "Custer Gallatin" or "custer-gallatin-national-forest".

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive, but the description adds real behavior: forecast horizon (~7 days, day and night), inclusion of source and fetch time, the paired-stream-gauge rule, and graceful degradation ('if the forecast cannot be read, the records still come back and say so'). That degradation clause in particular tells the agent how to interpret a partial result, which annotations cannot express.

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 a capitalized directive and ordered from trigger to output to input rules to exclusions. It is long, and the enumerated return fields read as a list dump, but with no output schema that enumeration is doing necessary work rather than padding.

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 or nested objects, so the description must carry the return contract and it does, down to source/fetch time and the three nearest free camps with URLs and dates. Combined with the failure-mode sentence, an agent has everything needed to call it and to explain the result to a user.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds constraints the schema does not encode: exactly one of camp, forest or town must be supplied (the schema declares zero required properties and no oneOf), and that a forest query resolves the forecast to one camp inside it, which is disclosed in the answer. State's disambiguation role is also restated usefully.

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 set: it returns the official NWS forecast plus the camp record's stay limit, fire rules, water, fee, land manager, wildfire reports, stream gauge and three nearest free camps. That level of specificity makes it clearly distinguishable from a plain weather tool like one_call or from camp_detail.

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?

Gives an unusually explicit trigger ('whenever someone asks about the weather in or near a national forest, BLM land or a camp'), forbids answering from memory or deferring to a weather site, and lists exclusions (road conditions, fire restrictions, permit prices). It stops short of naming a sibling alternative for the cases it does not cover, so it is clear but not fully routing.

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

All American Adventurer Camps 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?