American Adventurer Camps

Plan a four-night trip from the records

plan_four_nights

Read-onlyIdempotent

A trip letter: up to four nights at named camps from the records (free first, then unpriced, said so), a town run on day 3 with the recorded fuel, water and grocery, each camp's cost, stay limit, water, toilet and season for the date. Give forest_slug (a national forest) or town. start_date defaults to today; no night is put on a camp the record reads closed on that date, and a mostly-closed forest gets the earliest date its records say a camp opens. For the four places the game holds it adds a play link and a prompt with the plan folded in. All distances straight-line.

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": "plan_four_nights"
  }
}

Input Schema

Name	Required	Description
`town`	No	A town to plan around, like "Quartzsite" (use for BLM land).
`state`	No
`nights`	No
`start_date`	No	YYYY-MM-DD; default today.
`forest_slug`	No	National forest slug, like "custer-gallatin-national-forest".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/open-world, yet the description adds real behavior: free camps ranked before unpriced ones (and said so), a fixed day-3 resupply, closed-camp exclusion by date, fallback to the earliest open date for a mostly-closed forest, and straight-line distances. The one opaque phrase ('the four places the game holds') and absent cost units keep it from a 5.

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

Conciseness3/5

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

It is compact with no filler, but the information is crammed into one run-on sentence with stacked parentheticals, and the most important framing ('a trip letter') is an ambiguous fragment at the front. Readability suffers even though length is appropriate.

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

Completeness4/5

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

For a generator with five parameters, no output schema and 60% schema coverage, the description does describe the returned plan's contents (cost, stay limit, amenities, season, play link and prompt). The unaddressed gaps are the 'state' parameter and cost/units semantics.

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?

With 60% schema coverage, the description covers forest_slug (national forest) and town (BLM land, via the schema) and reinforces start_date defaulting to today and the four-night cap on nights. The 'state' parameter is unexplained in both schema and description, and no example pairings or precedence between town and forest_slug is given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description concretely enumerates what the tool produces: up to four nights at named camps from the records, a day-3 town run with fuel/water/grocery, per-camp cost, stay limit, water, toilet and season. That is specific enough to separate it from the lookup siblings (find_camps, camps_near, camp_detail), though the opening noun fragment 'A trip letter' never states the verb 'plan' and reads oddly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent what to supply ('Give forest_slug ... or town') but never says when to choose this over find_camps or camps_near, nor any preconditions such as requiring a known slug. There is no when-not guidance at all; usage is only inferable from the parameter hint.

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?