Skip to main content
Glama

Campsite details

get_campsite
Read-onlyIdempotent

Full details of one campsite: description, photos, check-in times, open season, every accommodation type with prices and rules, optional extras, the questions the campsite asks at booking, payment and deposit terms, and recent reviews.

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": {
      "campsite": "<campsite>"
    },
    "name": "get_campsite"
  }
}

Input Schema

NameRequiredDescriptionDefault
campsiteYesThe campsite slug, as returned by search_campsites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds substantial context beyond annotations by enumerating exactly what payload comes back (pricing, rules, booking questions, deposit terms, reviews), which matters since there is no output schema. It stops short of noting failure behavior for an unknown or stale slug.

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 sentence, front-loaded with the core purpose before the content list. The enumeration is long but each item is a distinct returned field, so it earns its space; a bulleted or tiered structure would read slightly better.

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?

For a one-parameter read tool with no output schema, the description carries the return-value burden well by naming the major sections of the response. An agent can tell whether this call will supply pricing, rules, or booking questions without inspecting anything else.

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?

There is only one parameter and schema coverage is 100%, with the schema already explaining that it is the slug from search_campsites. The description adds no format or validity detail beyond that, so the baseline of 3 applies.

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

Purpose4/5

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

The description opens with a specific verb+resource and scope: 'Full details of one campsite'. The enumeration of returned data makes it distinguishable from a list/search tool, though it never names search_campsites or the other siblings explicitly, so differentiation relies partly on the schema's slug hint.

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?

Usage is only implied by the word 'one campsite' and the singular required slug; nothing states when to call this versus search_campsites, check_availability, or get_quote. The prerequisite that a campsite slug must first come from search_campsites lives in the schema, not the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources