Skip to main content
Glama

outdoorithm

by io.github.outdoorithm

Get Campground Details

get_campground_details
Read-only

Get comprehensive details for a specific campground including amenities, reviews, safety, and seasonal ratings.

Returns ~80 curated fields (not the raw 214-column dump) including:

  • Identity, location, fees, site info

  • All amenity and activity booleans + descriptions

  • Review summaries, best campsites, common complaints, tips

  • Greenbook community safety (vibe score, flag status)

  • Seasonal LLM ratings (spring/summer/fall/winter)

  • Sentiment trend direction

  • Hero image with credits

Data coverage: a missing or empty field means the attribute isn't in our records, not that the feature is absent at the campground. Coverage varies by provider; the campground operator is the authoritative source.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campground_idYesUnique campground identifier (CUID format, e.g., "RecreationDotGov:232447:1074")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / campground_id / description
      Added value: +"Unique campground identifier (CUID format, e.g., \"RecreationDotGov:232447:1074\")"
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds valuable behavioral context: it returns a curated 80-field projection rather than a raw 214-column dump, explains that missing fields mean absence from records (not absence at the campground), and notes that coverage varies by provider. This goes well beyond the annotations.

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 front-loaded with a summary sentence, followed by a concise bullet-style list of returned categories, and ends with a short but crucial data-coverage caveat. Every section earns its place without 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?

Given the tool is read-only, has a single well-documented parameter, and includes an output schema, the description provides complete context: what the tool returns, which fields are in scope, and how to interpret missing data. No critical operational gaps remain.

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 already documents the single parameter campground_id with its CUID format and example, giving 100% schema coverage. The description does not add parameter-level detail, so the baseline of 3 is appropriate—the schema carries the burden.

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 uses a specific verb ('Get') and resource ('campground details'), and enumerates the exact content areas (amenities, reviews, safety, seasonal ratings). It clearly distinguishes from siblings like search_campgrounds by focusing on a single specific campground.

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 phrase 'for a specific campground' implies the tool is for retrieving details about one known campground, but it does not explicitly state when to prefer this over siblings like search_campgrounds or check_safety. No alternatives or exclusions are mentioned, though the context is clear enough to infer typical usage.

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

All outdoorithm toolsInspect
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