outdoorithm

by io.github.outdoorithm

Check Safety

check_safety

Read-only

Check campgrounds for safety issues, community atmosphere, and active alerts.

Checks:

Greenbook community safety (vibe scores, discrimination reports, flag status)
Active campground alerts (closures, restrictions) from enriched data
Red flag detection (prevents recommending unsafe campgrounds)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`campground_ids`	Yes	List of campground CUIDs to check

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJul 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / campground_ids / description
```
Added value: +"List of campground CUIDs to check"
```
First observedApr 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate a read-only, non-destructive operation. The description adds meaningful behavioral detail about data sources (Greenbook community safety, enriched alerts) and the red-flag detection purpose, going beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured: a leading summary sentence followed by three bullet points that enumerate checks. Every word adds value, with no redundancy or fluff.

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

Completeness5/5

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

The tool is simple (one parameter), has full schema coverage, and an output schema exists. The description covers what the tool does and why, making it complete for an agent to select and invoke correctly without further explanation.

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?

The input schema has 100% coverage for the single parameter, describing it as a list of campground CUIDs. The tool description adds no extra parameter semantics, so the baseline of 3 applies.

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 clearly states the tool checks campgrounds for safety issues, community atmosphere, and active alerts, with a specific list of check categories. This distinguishes it from sibling tools like check_availability and get_campground_details by focusing on safety and alerts.

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?

The description provides clear context on when to use the tool (when assessing safety before recommending a campground), but it does not explicitly mention alternatives or exclusions like 'use check_availability for availability'. Still, the scope is well-defined.

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

All outdoorithm tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools have clearly distinct purposes (search, details, availability, weather, etc.), but build_packing_list and get_gear_for_campground both deal with gear recommendations, and check_safety overlaps with the safety section in get_campground_details. However, the descriptions are detailed enough for an agent to choose correctly.

Naming Consistency4/5

Tool names follow a consistent verb_noun pattern (build_, calculate_, check_, compare_, find_, get_, prepare_, search_) with the exception of health_check, which reverses the order and breaks the pattern. This is a minor deviation.

Tool Count5/5

13 tools is well-scoped for a comprehensive outdoor trip planning server, covering search, details, availability, weather, safety, gear, and reservations without being excessive or sparse.

Completeness5/5

The server provides end-to-end coverage for planning a camping trip: search and filter campgrounds, get rich details, check availability, prepare reservations, evaluate safety, weather, drive times, gear recommendations, and packing lists. The only missing capability (direct booking) is intentionally excluded due to operator restrictions.

Resources

Need Help?