Skip to main content
Glama
deenesjakoruzh
campertunity

Campertunity MCP Server

Official
by campertunity
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Campertunity AIツール

世界中のキャンプ場を検索し、空き状況を確認し、予約するためのAIツールです。

エージェントスキルファイルと、AIを活用したキャンプ場検索のためのMCPサーバーが含まれています。

エージェントスキルファイル

このパッケージには、OpenClaw、Claude Code、Codex、およびSKILL.md形式をサポートするその他のエージェントプラットフォームと互換性のあるスキルファイルが含まれています。

スキルのインストール:

# OpenClaw
openclaw skills install campertunity

# Claude Code / other platforms
# Copy skills/campertunity/SKILL.md to your workspace skills directory

Related MCP server: Currents

MCPサーバー

クイックスタート

{
  "mcpServers": {
    "campertunity": {
      "command": "npx",
      "args": ["-y", "campertunity-ai-tools@latest"]
    }
  }
}

APIキー（オプション）

APIキーは不要です。より高いレート制限が必要な場合は、campertunity.com/mcpからキーを取得してください：

{
  "mcpServers": {
    "campertunity": {
      "command": "npx",
      "args": ["-y", "campertunity-ai-tools@latest"],
      "env": {
        "CAMPERTUNITY_API_KEY": "your_api_key_here"
      }
    }
  }
}

利用可能なツール

listing-search

フィルターと位置情報に基づいた検索を使用してキャンプ場を検索します。

パラメータ

型

説明

limit

number

返される結果数 (デフォルト: 50, 最大: 1000)

cursor

string

前回のレスポンスからのページネーションカーソル

startDate

string

空き状況の開始日 (YYYY-MM-DD)

endDate

string

空き状況の終了日 (YYYY-MM-DD)

adults

number

大人の人数 (デフォルト: 1)

children

number

子供の人数 (デフォルト: 0)

latitude

number

中心点の緯度

longitude

number

中心点の経度

radius

number

検索半径 (km) (デフォルト: 20)

region

string

地域/州 (緯度/経度がない場合はジオコーディングされます)

city

string

市区町村 (緯度/経度がない場合はジオコーディングされます)

country

string

国 (緯度/経度がない場合はジオコーディングされます)

countryCode

string

国コード (例: "US", "CA")

filters

string[]

フィルタリングするタグ (下記参照)

campgroundDescription

string

自然言語による説明

listing-details

特定のリスティングに関する詳細情報を取得します。

パラメータ

型

説明

listingId

string

リスティングのID

listing-availability

特定の日付のキャンプサイトの空き状況を確認します。

パラメータ

型

説明

listingId

string

リスティングのID

siteIds

string[]

オプションの特定のサイトID

startDate

string

開始日 (YYYY-MM-DD)

endDate

string

終了日 (YYYY-MM-DD)

listing-book

キャンプ場の予約URLを取得します。

パラメータ

型

説明

listingId

string

リスティングのID

startDate

string

開始日 (YYYY-MM-DD)

endDate

string

終了日 (YYYY-MM-DD)

adults

number

大人の人数 (デフォルト: 1)

children

number

子供の人数 (デフォルト: 0)

フィルタータグ

サイトタイプ: tent, rv, lodging, glamping, cabin

アクセス: driveIn, walkIn, equestrian, boat

アクティビティ: biking, boating, fishing, hiking, horsebackRiding, paddling, windSports, surfing, swimming, whitewaterPaddling, wildlifeWatching

設備: picnicTable, fires, toilets, outhouse, potableWater, petFriendly, rvHookup, rvSanitation, trash, showers, wifi, handicap

地形: beach, cave, desert, forest, hotSpring, lake, river, swimmingHole, waterfall, creek

データに関する注意

データは複数のソースから収集され、AIによって強化されています。データの再配布、キャッシュ、または変更は行わないでください。常にサーバーを通じてリアルタイムのデータを使用してください。

詳細については、campertunity.comをご覧ください。

Available Tools

4 tools
place-availabilityD
ParametersJSON Schema
NameRequiredDescriptionDefault
placeIdYesThe id of the place to check availability for.
siteIdsNoThe ids of the sites to check availability for.
startDateYesThe start date to check availability for. Format: YYYY-MM-DD
endDateYesThe end date to check availability for. Format: YYYY-MM-DD

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

place-bookD
ParametersJSON Schema
NameRequiredDescriptionDefault
placeIdYesThe id of the place to book.
startDateNoThe start date of the booking. Format: YYYY-MM-DD
endDateNoThe end date of the booking. Format: YYYY-MM-DD
adultsNoNumber of adults. Default is 1.
childrenNoNumber of children. Default is 0.

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

place-detailsD
ParametersJSON Schema
NameRequiredDescriptionDefault
placeIdYesThe id of the place to get details for.

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 4 tool updates
    • First observedplace-availability
    • First observedplace-book
    • First observedplace-details
    • First observedplace-search
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.1/5.0
Disambiguation4/5

The tools have distinct purposes based on their names: search for finding places, details for getting information, availability for checking status, and book for making reservations. While the lack of descriptions introduces some ambiguity about exact boundaries, the core actions (search, get, check, reserve) are clearly differentiated.

Naming Consistency5/5

All tools follow a perfect 'place-verb' pattern with hyphenated naming (place-search, place-details, place-availability, place-book). This consistency makes the tool set predictable and easy to understand at a glance.

Tool Count5/5

With 4 tools, this server is well-scoped for a camping/place booking domain. Each tool covers a fundamental operation (search, view details, check availability, book), and there are no extraneous tools—each earns its place in the workflow.

Completeness4/5

The tool set covers the essential CRUD-like operations for a booking system: search (discover), details (read), availability (check), and book (create). A minor gap is the lack of update/cancel or delete operations for bookings, but agents can still complete core workflows with the provided tools.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/campertunity/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server