Skip to main content
Glama

Luxury Travel Tools by Global Lux Agency

Luxury safari planner: where and when to go

safari-planner
Read-onlyIdempotent

Ranks 11 well-known safari regions (Masai Mara, Serengeti, Okavango Delta, Greater Kruger and Sabi Sand, Madikwe, Eastern Cape, South Luangwa, Hwange, Etosha, Bwindi, Volcanoes) for a month of travel and priorities, using sourced best and rainy seasons and migration timing, and suggests a route with nights per camp. Wildlife timing varies year to year. No prices, availability, health or entry advice. Web page: https://globalluxagency.com/tools/safari-planner

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "safari-planner"
  }
}

Input Schema

NameRequiredDescriptionDefault
paceNorelaxed ≈ 4, balanced ≈ 3, active ≈ 2 nights per camp (a planning choice).balanced
beachNoPriority: Beach extension.
monthNoMonth of travel, 1 (January) to 12 (December).
familyNoFamily with children under 15: favours malaria-free reserves and excludes gorilla treks (minimum age 15).
nightsNoNights in total, including any beach extension.
bigCatsNoPriority: Big cats.
walkingNoPriority: Walking safaris.
gorillasNoPriority: Gorilla trekking.
migrationNoPriority: Great Migration.
malariaFreeNoMalaria-free only: only regions widely described as malaria-free (not health advice).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety bar is low. The description still adds real value beyond them: it discloses the data basis (sourced best/rainy seasons and migration timing), an epistemic caveat ('Wildlife timing varies year to year'), and hard scope limits on prices, availability, health and entry advice. It does not describe output structure in detail, but the shape of the answer is sketched.

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?

Front-loads the core capability (what is ranked, on what basis) before caveats and the URL. Dense but not padded; the region list is long yet functional. The trailing web page link earns little for an agent, a minor cost.

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?

Ten optional parameters with defaults, no output schema, so the description must convey the return shape — and it does, naming both a ranking and a route with nights per camp. Caveats about year-to-year variability and excluded topics set appropriate expectations. Only the detailed output fields (per-region scoring, why-ranked) remain unspecified.

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%, including a documented enum for pace and explicit defaults, so the schema carries parameter meaning on its own. The description adds only the general notion of 'priorities' and 'nights per camp' rather than per-parameter semantics. Baseline 3 applies when the schema does the heavy lifting.

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?

Specific verb ('ranks') plus a concrete resource set (11 named safari regions) and the inputs it ranks on (month, priorities, seasons, migration timing). An agent knows exactly what comes back: a regional ranking plus a suggested route with nights per camp. It does not name the closest sibling, 'where-to-go-on-holiday-by-month', so a boundary judgment is left to inference.

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?

Gives clear conditions for use (a month of travel plus stated priorities) and explicit scope exclusions: 'No prices, availability, health or entry advice', which tells the agent which other tools to reach for. It stops short of naming an alternative for the generic 'where to go' case, so routing between it and that sibling is implied rather than stated.

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