American Adventurer Camps

One camp record in full

camp_detail

Read-onlyIdempotent

The full record for one camp by slug: cost and its evidence, water, nearest toilet, recorded rules and stay limit, the season on a date (default today, UTC), the nearest fuel, water, grocery and dump station with straight-line miles, and what is unrecorded. Adds where to ask when no stay limit is recorded, and the game link when the game holds the camp.

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": {
      "slug": "<slug>"
    },
    "name": "camp_detail"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No	YYYY-MM-DD for the season reading; default today.
`slug`	Yes	The camp record id from find_camps.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: distances are straight-line rather than driving, the season reading defaults to today in UTC, unrecorded fields are surfaced, and there is a fallback pointer to 'where to ask' when no stay limit exists. Some phrasing ('the game link when the game holds the camp') stays opaque.

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?

The purpose is front-loaded in the opening clause and every listed item corresponds to a real returned field, so little is wasted. The second half is a long comma-chained list that would read faster as a structured enumeration, which keeps it short of a 5.

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, the description carries the burden of describing return content and does so thoroughly, including edge-case behavior for missing data. Only the vague 'game link' clause leaves an agent guessing about a returned field.

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 both parameters are already documented, and the description still adds meaning by explaining that date drives the season reading (default today, UTC) rather than being a generic filter. That is a genuine semantic addition over the schema text.

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 and resource ('The full record for one camp by slug') and enumerates the returned content, so an agent can tell it is the detail lookup rather than a search. It never names the sibling tools (find_camps, camps_near) that would be the alternatives, so differentiation is implied rather than explicit.

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?

Usage is only implied: the slug reference and the schema note that the id comes from find_camps hint at a search-then-detail flow. There is no explicit statement of when to choose this over camps_near or one_call, and no exclusions or prerequisites are given.

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?