Pitchup.com MCP server

Get a campsite

get_campsite

Read-only

Retrieve a campsite's details by slug, including pitch types, rules, dates, and policies. Add contact details when needed; payment settings are never returned.

Instructions

One campsite by slug: state, currency, pitch types, languages, child and infant age limits, arrival and departure times, opening dates, rating, notices and policies. Payment settings are never returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_campsite"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Campsite slug (from list_campsites)
`include_contact_details`	No	Include the campsite's email, manager email, phone numbers and postal address, and stop redacting emails, phone numbers, UK postcodes and UK registrations in notices and policies

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine behavioral context annotations do not carry: the explicit exclusion 'Payment settings are never returned' and a preview of the returned field set (state, currency, times, ratings, notices/policies).

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?

A single front-loaded sentence with zero filler; the scope ('one campsite by slug') comes first and the field list second. The field enumeration is dense but every item is substantive information about the result.

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

Completeness4/5

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

With no output schema, the description usefully previews the returned shape and flags the payment-settings exclusion, which an agent would otherwise have to discover empirically. It omits any note on invalid-slug behavior or the contact-detail toggle's effect, though the schema covers the latter.

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?

Schema description coverage is 100%, so both parameters (including include_contact_details and its redaction implications) are fully documented in the schema. The description's 'by slug' adds nothing beyond that, so the baseline 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 states a specific verb/resource pairing ('One campsite by slug') and enumerates the returned facets, making it immediately distinguishable from sibling list tools like list_campsites and list_pitch_types without opening schemas.

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 singular 'One campsite by slug' implies this is the single-item lookup versus list_campsites, but the description never explicitly states when to use it or names an alternative. Usage is inferable only from the noun phrasing and the required slug parameter.

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

Deploy Server