American Adventurer Camps

Water and gas math for a rig

rig_math

Read-onlyIdempotent

Plain arithmetic: how many nights a tank of water lasts for a number of people at a stated use per person per day, and how far a tank of gas goes at a stated mileage. Nothing is read from a record. Any default rate (1 gallon per person per day, 13 mpg, the game's numbers) is labeled in the answer as an assumption you can change; it is not a fact about a place.

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": {
      "water_gal": "<water_gal>",
      "gas_gal": "<gas_gal>",
      "people": "<people>"
    },
    "name": "rig_math"
  }
}

Input Schema

Name	Required	Description
`mpg`	No	Optional: your rig's miles per gallon. Default 13 (an assumption, the game's pavement number).
`nights`	No	Optional: nights planned, to say whether the water is enough.
`people`	Yes	How many people use the water.
`gas_gal`	Yes	Gallons of gas in the tank.
`water_gal`	Yes	Gallons of water aboard.
`water_gal_per_person_per_day`	No	Optional: gallons each person uses a day. Default 1 (an assumption).

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 declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. Beyond that, the description discloses genuinely useful output behavior: any default rate is echoed in the answer and labeled as a changeable assumption rather than a fact about a location. It does not describe units or result shape in more detail, but the assumption-labeling is the behavior an agent most needs.

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 core purpose is front-loaded in the first clause, and the sentences are short and purposeful. There is some repetition between the opening 'Plain arithmetic' framing and the closing note about assumptions, but no sentence is wasted outright.

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 six parameters, no output schema, and no nested structures, the description adequately covers what the tool computes and what its answer contains (labeled assumptions). Return-value detail is partially carried by the description since no output schema exists, leaving a small gap on result format.

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%, so every parameter including the two defaults (1 gal/person/day, 13 mpg) is already documented in the schema. The description adds only the framing that those defaults are assumptions rather than facts, which is mild added meaning against a schema that already does the heavy lifting.

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?

The description states a specific computation in concrete terms: nights of water at a stated per-person rate and distance on a tank of gas at a stated mileage. It also explicitly disclaims record lookup ("Nothing is read from a record"), which cleanly separates it from lookup siblings like camp_detail or camps_near.

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?

It gives a clear condition for use — plain arithmetic on user-supplied numbers, not facts about a place — which implicitly steers the agent away from the record-reading tools. It stops short of naming an explicit alternative or stating exclusions in so many words.

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?