American Adventurer Camps

Find public-land camps

find_camps

Read-onlyIdempotent

Search the American Adventurer records of public-land camps by name or place word, state, cost (free, fee, unpriced, license) and water. Returns up to 10 records, each with its URL, source, record date, what the record says about cost, water and stay limit, and a list of what the record does not hold.

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

Input Schema

Name	Required	Description
`q`	No	A camp or place name word, like "hyalite".
`cost`	No
`limit`	No
`state`	No	Two-letter state, like "MT".
`water`	No	True to keep only camps whose record names water.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.7/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 and non-destructive, so the description focuses on what annotations cannot say: the result cap, the fields returned (URL, source, record date, cost, water, stay limit), and notably a list of what each record lacks. That last detail usefully warns the agent about sparse data. It never contradicts the annotations.

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?

Two sentences, front-loaded with the search scope before the return shape. The return-field enumeration is long but earns its place because there is no output schema.

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?

With no output schema, describing the returned fields and their gaps is the right fill. Remaining gaps: no statement about whether an empty query (all parameters optional) is permitted, and no behavior for results beyond the cap. Both are minor for a read-only search tool.

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 60% and the schema already documents q, state, water and limit; the description mostly restates those facets. It does add the cost vocabulary (free, fee, unpriced, license), which the schema gives only as a bare enum, but it does not explain what those categories mean or how they combine with other filters.

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 names a specific verb (search) and resource (American Adventurer records of public-land camps) and enumerates the searchable facets: name/place word, state, cost, water. That distinguishes it reasonably from proximity siblings like camps_near and free_camping_near_town, though the differentiation is implicit rather than stated.

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 attribute-based filtering implies when to reach for this tool over camps_near or camp_detail, but no alternative is named and no when-not condition is given. An agent must infer that this is the text/attribute search versus the proximity search.

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?