American Adventurer Camps

Where a Dispersed 3D trip is

trip_status

Read-onlyIdempotent

Read-only status of a Dispersed 3D trip from its 8-character code (like ABCD-2345): the day and clock of the last saved move, the last few moves, finished or not, the end-card gas and water once the trip is over, and the link to watch it. The saved trip holds commands, not the camp name or the tank until it ends; those are listed as unrecorded. Never changes a trip.

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": {
      "code": "<code>"
    },
    "name": "trip_status"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	The trip code the game shows: 8 characters, a dash allowed after the fourth.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and openWorld, so the description only needs to add context — and it does, disclosing a data-availability quirk (saved trips store commands, not camp name or tank, until completion) and that end-card values appear only after the trip finishes. 'Never changes a trip' is a mild restatement of readOnlyHint, and error behavior for a bad code is unaddressed.

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 purpose, followed by the return contents, then the caveat and the read-only reassurance. Dense and mostly waste-free, though the closing 'Never changes a trip' slightly duplicates the readOnlyHint annotation.

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 returns and does so field-by-field, including the watch link and the condition under which end-card values exist. Remaining gaps are minor: it doesn't say how many 'last few moves' are returned or what happens for an unrecognized code.

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 already documents the 8-character/dash-after-fourth format. The description reinforces this with a concrete example ('like ABCD-2345') and the phrase 'the trip code the game shows', which helps the agent locate the value, but adds no format or validation detail beyond the schema — 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?

States a specific verb and resource ('Read-only status of a Dispersed 3D trip') keyed to a concrete identifier, then enumerates exactly what the status contains: last move time, recent moves, completion state, end-card gas/water, and watch link. Nothing about this overlaps the sibling camp, weather, or leaderboard tools, so an agent can select it unambiguously.

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?

Clear context for use — look up a trip by its 8-character code — plus an important expectation-setting caveat that camp name and tank are 'unrecorded' until the trip ends, which tells the agent not to treat missing fields as an error. It stops short of naming when to prefer another tool or what to do with an invalid/unknown code.

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?