Fortitude21 Dangerous Goods Tools

Water or fuel quantity in jerry cans

jerry_can_quantity

Read-onlyIdempotent

Work out how much water (people x days x litres a day, Sphere and national advice) or fuel (distance and consumption, or hours and consumption, or generator kVA) to hold, with a margin, and how many jerry cans that takes.

Input Schema

Name	Required	Description
`can`	No	A product slug from our range to size in
`kva`	No	Fuel, generator scenario: generator rating in kVA
`days`	No	Number of days to cover
`load`	No	Generator scenario: load in per cent, with kva
`mode`	No	water or fuel
`rate`	No	Water, custom scenario: litres a person a day
`hours`	No	Fuel: running hours, with consumption in L/h
`units`	No	us for miles and US gallons
`weeks`	No	Number of weeks, if no days
`people`	No	Water: number of people to supply
`volume`	No	Litres to hold directly, instead of working it out from a scenario
`reserve`	No	Margin in per cent
`units_n`	No	Vehicles, boats or machines
`distance`	No	km (miles with units=us)
`scenario`	No	Water: relief, acute, protracted, survival, nl, se, no, fi, dk, de, custom. Fuel: road, overland, marine, generator, agri, direct.
`returnTrip`	No	Fuel, overland scenario: 1 to count the return leg
`consumption`	No	L/100 km (distance) or L/h (time); with units=us, miles per US gallon or US gallons an hour

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 29, 2026
- addedInput schema / properties / days / description
```
Added value: +"Number of days to cover"
```
- addedInput schema / properties / hours / description
```
Added value: +"Fuel: running hours, with consumption in L/h"
```
- addedInput schema / properties / kva / description
```
Added value: +"Fuel, generator scenario: generator rating in kVA"
```
- addedInput schema / properties / mode / description
```
Added value: +"water or fuel"
```
- addedInput schema / properties / people / description
```
Added value: +"Water: number of people to supply"
```
- addedInput schema / properties / volume / description
```
Added value: +"Litres to hold directly, instead of working it out from a scenario"
```

Changed7 schema fields changedOct 13, 2026

addedInput schema / properties / can

Added value: +{
+  "description": "A product slug from our range to size in",
+  "type": "string"
+}

changedInput schema / properties / consumption / description

Previous value: -"L/100 km or L/h"New value: +"L/100 km (distance) or L/h (time); with units=us, miles per US gallon or US gallons an hour"

addedInput schema / properties / load

Added value: +{
+  "description": "Generator scenario: load in per cent, with kva",
+  "type": "number"
+}

addedInput schema / properties / rate

Added value: +{
+  "description": "Water, custom scenario: litres a person a day",
+  "type": "number"
+}

addedInput schema / properties / returnTrip

Added value: +{
+  "description": "Fuel, overland scenario: 1 to count the return leg",
+  "enum": [
+    "0",
+    "1"
+  ],
+  "type": "string"
+}

addedInput schema / properties / units

Added value: +{
+  "description": "us for miles and US gallons",
+  "enum": [
+    "metric",
+    "us"
+  ],
+  "type": "string"
+}

addedInput schema / properties / weeks

Added value: +{
+  "description": "Number of weeks, if no days",
+  "type": "number"
+}

First observedOct 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is fully covered. The description adds genuinely new behavioral context: results include 'a margin', and the water path follows 'Sphere and national advice' standards, plus it hints at the return value ('how many jerry cans that takes'). It stops short of describing defaults or units of the returned figures.

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?

A single front-loaded sentence that leads with the deliverable and then the scenarios; there is no filler. It is dense to the point of being parenthetical-heavy, which slightly hurts scanning, but every clause carries information.

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

Completeness3/5

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

For a 17-parameter tool with zero required parameters and no output schema, the description covers the major modes but leaves key gaps: it does not say which parameters are needed per scenario, how days vs weeks or volume vs scenario interact, or what the returned quantity looks like. An agent could pick the wrong input set and still be within the text of the description.

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 per-parameter meaning is already documented and the baseline is 3. The description goes beyond that by explaining how parameters combine into a computation (people x days x litres for water; distance/consumption, hours/consumption, or kVA/load for fuel), which is coordination semantics the flat schema does not convey.

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 states a concrete verb ('work out') and a concrete resource ('how much water ... or fuel to hold, and how many jerry cans that takes'), and it even sketches the calculation inputs (people x days x litres, distance/consumption, generator kVA). The purpose is unmistakable, but it never contrasts itself with the sibling tools (bund_size, adr_1000_points, ibc_inspection_dates), so there is no explicit sibling differentiation.

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 parenthetical breakdown implies which input family belongs to which scenario (water = people/days/rate, fuel = distance/consumption, hours/consumption, or kVA), which is useful routing. However there is no explicit statement of when to use this versus an alternative, no prerequisite conditions, and no exclusion such as what to do if you already know the volume.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fortitude21 Dangerous Goods Tools 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?