Skip to main content
Glama
campertunity

Campertunity MCP Server

Official
by campertunity

place-book

Book campsites and outdoor accommodations by specifying place ID, dates, and number of guests for camping reservations.

Input Schema

TableJSON 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.

Implementation Reference

  • The main handler logic for the 'place-book' tool. It makes a POST request to the Campertunity API's /place/book endpoint with booking details and returns the response as JSON or an error.
    async ({ placeId, startDate, endDate, adults, children }) => {
      try {
        const availability = await campertunityClient.post(`/place/book`, {
          placeId,
          startDate,
          endDate,
          adults,
          children,
        });
        return {
          content: [{ type: 'text', text: JSON.stringify(availability), mimeType: 'application/json' }],
        };
      } catch (error) {
        return {
          content: [{ type: 'text', text: 'Error: ' + (error as Error).message }],
          isError: true,
        };
      }
    }
  • Zod schema defining the input parameters for the 'place-book' tool: placeId (required), startDate/endDate (optional), adults/children (with defaults).
    {
      placeId: z.string().describe('The id of the place to book.'),
      startDate: z.string().optional().describe('The start date of the booking. Format: YYYY-MM-DD'),
      endDate: z.string().optional().describe('The end date of the booking. Format: YYYY-MM-DD'),
      adults: z.number().default(1).describe('Number of adults. Default is 1.'),
      children: z.number().default(0).describe('Number of children. Default is 0.'),
    },
  • The placeBookTool function that registers the 'place-book' tool on the MCP server using server.tool(), including the tool name, input schema, and handler.
    export const placeBookTool = (server: McpServer, campertunityClient: CampertunityClient) => {
      server.tool(
        'place-book',
        {
          placeId: z.string().describe('The id of the place to book.'),
          startDate: z.string().optional().describe('The start date of the booking. Format: YYYY-MM-DD'),
          endDate: z.string().optional().describe('The end date of the booking. Format: YYYY-MM-DD'),
          adults: z.number().default(1).describe('Number of adults. Default is 1.'),
          children: z.number().default(0).describe('Number of children. Default is 0.'),
        },
        async ({ placeId, startDate, endDate, adults, children }) => {
          try {
            const availability = await campertunityClient.post(`/place/book`, {
              placeId,
              startDate,
              endDate,
              adults,
              children,
            });
            return {
              content: [{ type: 'text', text: JSON.stringify(availability), mimeType: 'application/json' }],
            };
          } catch (error) {
            return {
              content: [{ type: 'text', text: 'Error: ' + (error as Error).message }],
              isError: true,
            };
          }
        }
      );
    };
  • src/index.ts:24-24 (registration)
    Invocation of placeBookTool in the main server file, which triggers the registration of the 'place-book' tool.
    placeBookTool(server, campertunityClient);
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.

Install Server

Other Tools

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