Skip to main content
Glama

Camping Australia

by au.com.trip-planner

Search campsites

search_campsites
Read-onlyIdempotent

Search for campsites, caravan parks, or accommodation by location, features, and other criteria. Use this when the user asks to find a place to stay, camp, or explore. Returns a list of matching entities with names, locations, ratings, features, and images.

COVERAGE: Australia (default), the United States (federal, BLM, national-forest campgrounds + free camping), Canada, New Zealand, Argentina AND Chile (campgrounds + free camping). Set the 'country' parameter to 'US' for United States, 'CA' for Canada, 'NZ' for New Zealand, 'AR' for Argentina, 'CL' for Chile, 'AU' for Australia — results never mix countries.

IMPORTANT — Feature filtering: When users mention specific requirements (pets, pools, toilets, etc.), you MUST pass the correct feature name(s) in the 'features' array. Only campsites that have ALL requested features will be returned.

AVAILABLE FEATURE NAMES (use these exact strings): Amenities: Toilets, Showers, Hot Showers, Drinking Water, Power, WiFi Internet, Laundromat, Dump Point, Camp Kitchen Activities: Fishing Spot, Beach Fishing, Swimming, Walking, Boating, Boat Ramp, Bird Watching Accommodation: Caravans, Caravan Park, Tent Site, Campground, Cabins, Free Camping, Showground Facilities: BBQ, Fire Place, Shade, Picnic Tables, Children's Play Facility, Swimming Pool Rules: Pets Welcome, No Pets, Accessible, Camping Fee, Mobile Phone Coverage

CRITICAL — Pet policy:

  • 'dog friendly' / 'pets allowed' / 'pet friendly' → use feature 'Pets Welcome'

  • NEVER recommend a campsite with 'No Pets' feature to someone wanting pets

  • If the user asks for pet-friendly, ALWAYS include 'Pets Welcome' in features array

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return (default 6, max 20)
queryNoFree-text search for campsite name or location (e.g. 'Byron Bay', 'Moab', 'Banff', 'Queenstown', 'Bariloche', 'Torres del Paine', 'Central Coast'). Do NOT put feature requirements here — use the 'features' parameter instead.
stateNoAUSTRALIA ONLY — state abbreviation (e.g. 'NSW', 'VIC', 'QLD'). For US/CA/NZ searches use 'query' or near_latitude/near_longitude instead.
regionNoRegion name to search within (e.g. 'South Coast', 'Blue Mountains')
countryNoWhich country's campsites to search. Set 'US' for United States, 'CA' for Canada, 'NZ' for New Zealand, 'AR' for Argentina, 'CL' for Chile, 'AU' for Australia. Defaults to 'AU'. Results NEVER mix countries — always set this to match the location the user is asking about.
featuresNoREQUIRED features the campsite MUST have. Use exact feature names from the list above. e.g. ['Pet Friendly', 'Toilets', 'Swimming Pool']. All listed features must be present on a campsite for it to be returned.
radius_kmNoSearch radius in kilometres (default 50, use 100-150 for broader search)
entity_typeNoFilter by listing type. Use when the user specifies what kind of place they want: - 'free_camping' — free bush camps, rest areas with overnight stays - 'caravan_park' — caravan parks with powered/unpowered sites - 'campground' — managed campgrounds (national parks etc) - 'accom' — accommodation (cabins, lodges, holiday parks) - 'campsite' — individual campsites - 'tours' — tours and activities - 'poi' — points of interest, day-use areas, lookouts, picnic spots (NO overnight camping) If the user just says 'camping' or 'campsites', do NOT set this — search all types. If the user asks for 'free camping', set to 'free_camping'. If the user asks for 'things to do' or 'activities', set to 'tours'. If the user asks for 'day trips' or 'picnic spots', set to 'poi'.
near_latitudeNoLatitude for proximity search. AU: -33.8688 Sydney. US: 38.5733 Moab, 37.8651 Yosemite Valley. CA: 51.1784 Banff, 49.2827 Vancouver. NZ: -45.0312 Queenstown, -38.1368 Rotorua, -43.5321 Christchurch, -36.8485 Auckland. AR: -41.13 Bariloche, -32.89 Mendoza, -50.34 El Calafate. CL: -41.32 Puerto Varas, -39.27 Pucón, -51.73 Puerto Natales / Torres del Paine. Set 'country' to match.
near_longitudeNoLongitude for proximity search. AU: 151.2093 Sydney. US: -109.5498 Moab, -119.5383 Yosemite Valley. CA: -115.5708 Banff, -123.1207 Vancouver. NZ: 168.6626 Queenstown, 176.2497 Rotorua, 172.6362 Christchurch, 174.7633 Auckland. AR: -71.31 Bariloche, -68.84 Mendoza, -72.28 El Calafate. CL: -72.99 Puerto Varas, -71.98 Pucón, -72.51 Puerto Natales / Torres del Paine. Set 'country' to match.

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, not destructive), the description discloses critical behavioral traits: 'results never mix countries', 'Only campsites that have ALL requested features will be returned', and the pet policy with 'NEVER recommend a campsite with No Pets'. This adds substantial context not present in annotations or schema.

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 description is quite long but well-structured with clear section headers (COVERAGE, IMPORTANT, CRITICAL). It front-loads the purpose in the first sentence. The length is justified by the need to explain feature names and pet policy, but it still could be trimmed without losing essential info.

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 10 parameters, no output schema, and no required params, the description is remarkably complete. It explains country coverage, feature filtering behavior, pet policy, entity types, and provides coordinate examples for near_latitude/longitude. No critical gaps remain for an agent to misunderstand tool usage.

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?

The schema already provides 100% parameter descriptions, so the baseline is 3. The description adds extra semantic depth through the AVAILABLE FEATURE NAMES list, the pet-policy mapping, and entity_type examples (free camping, caravan parks, etc.), which go beyond the schema's per-parameter descriptions.

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 'Search for campsites, caravan parks, or accommodation by location, features, and other criteria' — a specific verb+resource. It also distinguishes itself from sibling tools with the directive 'Use this when the user asks to find a place to stay, camp, or explore.'

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 'Use this when...' sentence provides clear contextual guidance, and the coverage section explains when to set the country parameter. However, it does not explicitly mention alternatives or exclusions (e.g., 'use search_campervans for campervans'), so it lacks fully explicit when-not guidance.

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

All Camping Australia 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.3/5.0
Disambiguation5/5

Each tool targets a distinct operation: bk_* for Bookeasy booking workflows (add, checkout, guest, promo, search operators/content), get_* for retrieval, search_* for different domains (campsites, campervans, products), and find_nearest_toilets and recommend_gear for specific niche queries. No significant overlap.

Naming Consistency5/5

Naming follows a consistent pattern: bk_ prefix for Bookeasy tools, then verb_noun (e.g., bk_cart_add, bk_search_operators). Non-bk tools use get_ or search_ prefixes. All snake_case, predictable and clear.

Tool Count5/5

18 tools cover a broad scope (accommodation search, campervan rental, public toilets, weather, gear, products, and full booking lifecycle) without bloat. Each tool earns its place; the count is well-scoped for the domain.

Completeness4/5

The tool set covers most user needs: listing, searching, booking, weather, gear, product sales. Minor gaps (e.g., no tool for cancelling/viewing past bookings) but these are likely handled externally via the booking platform. The core workflows are well-supported.

Resources