# find_destination

Discover travel destinations when the user does NOT know where to go. This is a destination EXPLORATION tool. WHEN TO USE THIS TOOL (CRITICAL): - The user does NOT specify a destination: "Where should I go?", "Best deals from NYC" - The user wants inspiration based on criteria: "Beach destinations", "Somewhere warm", "Cheap flights from SF" - The user wants to compare multiple destination options from their origin - The user previously asked for destination recommendations and wants pricing for those options WHEN NOT TO USE THIS TOOL — USE flight_calendar INSTEAD: - The user specifies BOTH an origin AND a destination → use flight_calendar - Examples that should use flight_calendar, NOT this tool: • "Flights from Paris to Barcelona" → flight_calendar • "Find me a flight from JFK to CDG" → flight_calendar • "Cheapest flight from LA to Miami in June" → flight_calendar • "Paris to BCN for a weekend in April" → flight_calendar • "What are the cheapest dates to go to NYC from Paris?" → flight_calendar - If the user names a specific city/airport as destination, that means they KNOW where to go → flight_calendar IMPORTANT - DATES: All dates in query parameters (departure_dates, departure_date_ranges, return_dates, return_date_ranges) MUST be in the future. Never use past dates. Please fill as much as possible search parameters based on user intent to get best results. IMPORTANT - RE-CALL THIS TOOL when the user: - Asks for a different type of destination (beach, city trip, ski, etc.) - Asks for different dates while still exploring - The user is already in fullscreen mode in the widget CORE FUNCTIONALITY: - REQUIRED: User's origin location (LLM identifies ALL nearby airports) - OPTIONAL: Destination filtering by specific airports/cities OR omit for global discovery mode - Destination Discovery Mode: When destinations is omitted/empty, searches ALL destinations globally - Flexible dates and stay durations for exploring options - Filter by budget, direct flights preference, and locale - By default, please search roundtrip flights unless user specifies one-way AIRPORT IDENTIFICATION - CRITICAL: LLM MUST identify and recommend ALL relevant airports for user's origin location: - "New York": ["JFK", "LGA", "EWR"] - "London": ["LHR", "LGW", "STN", "LTN", "LCY"] - "Paris": ["CDG", "ORY"] - "Tokyo": ["NRT", "HND"] - "Chicago": ["ORD", "MDW"] - "Los Angeles": ["LAX"] - "San Francisco": ["SFO"] DESTINATION FILTERING - INTELLIGENT INTERPRETATION: Destinations can be specified using IATA airport codes OR city codes (3 letters). You can mix both types: - Airport codes: ["JFK", "LAX", "LHR"] - searches specific airports - City codes: ["NYC", "LON", "PAR"] - searches all airports in those cities DESTINATION LIST - CRITICAL: When users mention criteria that imply a type of destination, the LLM MUST generate the appropriate list: - "Sunny places in winter": ["MIA","MCO","SAN","PHX","HNL","CUN","PUJ","PTY","LIM","GIG"] - "Somewhere in Asia": ["NRT","HND","ICN","PVG","PEK","HKG","SIN","BKK","KUL","MNL"] - "Beach destinations": ["MIA","SAN","HNL","CUN","PUJ","SJU","NAS","MBJ"] - "European capitals": ["LHR","CDG","FRA","MAD","FCO","AMS","BRU","VIE","PRG","CPH"] If no filtering is specified ("anywhere", "surprise me"), leave destinations empty for global discovery. TYPICAL USE CASES: 1. "Where should I travel from NYC next month?" → origins: ["JFK","LGA","EWR"], destinations: [] 2. "I want to go somewhere warm from Chicago for a week in December" → origins: ["ORD","MDW"], destinations: [warm destinations] 3. "Best weekend getaways from Boston?" → origins: ["BOS"], destinations: [] 4. "Beach vacation from Seattle in summer under $600" → origins: ["SEA"], destinations: [beach destinations] IMPORTANT: Always provide ALL airports for origins to maximize search results. Cost: 1 credit per call.

Agent View of the PolicyLayer registry record for `find_destination`. HTML page: https://policylayer.com/tools/com-gojinko-mcp-jinko/find-destination

## Facts

- Tool: `find_destination`
- Server: Jinko MCP (`https://mcp.gojinko.com`) — https://policylayer.com/tools/com-gojinko-mcp-jinko.md
- Homepage: https://github.com/https://mcp.gojinko.com
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 12 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `locale` | string | no | User's BCP 47 locale inferred from the conversation (e.g. "fr-FR", "en-US", "ja-JP"). Used for formatting dates, numbers, and selecting currency. Infer from the |
| `origins` | array | yes | REQUIRED. Array of origin IATA codes (3-letter uppercase), representing either airports or cities where the trip starts. The LLM MUST detect and include all rel |
| `sort_by` | string | no | Sorting preference for search results. Options: "lowest" (cheapest first, default) or "recommendation" (best overall balance of price, duration, and stops). |
| `currency` | string | no | ISO 4217 currency code for displaying prices (e.g. "EUR", "USD", "GBP"). Infer from the user's country or locale. If the user mentions a specific currency, use |
| `max_price` | number | no | Maximum total price per passenger, the currency is user default currency. Filters out results exceeding the limit. Example: 500 = limit of $500/€500/£500 per pe |
| `stay_days` | integer | no | Exact number of days to stay at the destination. Used with a departure date to automatically compute the return date. Example: 7 = one-week trip; 3 = weekend ge |
| `trip_type` | string | yes | REQUIRED. Type of trip: "oneway" for single-leg flights, or "roundtrip" for return flights. |
| `cabin_class` | string | no | Preferred cabin class. Options: "economy", "premium_economy", "business", or "first". Filters results accordingly. |
| `direct_only` | boolean | no | When true, only returns nonstop (direct) flights. Useful for avoiding layovers or minimizing total travel time. |
| `user_intent` | string | no | A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used t |
| `destinations` | array | no | OPTIONAL. Array of destination IATA codes (3-letter uppercase), representing either airports or cities. When a city code is provided, the LLM MUST expand it to |
| `return_dates` | array | no | List of specific return dates for round-trip searches (YYYY-MM-DD). Must be after the corresponding departure dates. Supports multiple options (OR logic). Examp |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "find_destination",
    "arguments": {
      "origins": [],
      "trip_type": "<trip_type>"
    }
  }
}
```

## Why find_destination is rated Low

This tool retrieves and queries travel destination information to help users explore options. It performs no side effects, does not modify data, does not execute external operations with variable outcomes, does not delete data, and does not process payments. It is purely informational/exploratory in nature, fitting squarely within the Read category.

From the tool's own definition: "Tool name 'find_destination' and description states it is a 'destination EXPLORATION tool' that helps users 'Discover travel destinations' and 'compare multiple destination options' based on criteria like budget, weather, and origin city."

Risk signals: High parameter count (22 properties)

## Use case

AI agents call find_destination to retrieve information from Jinko MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Jinko MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_destination": {}
  }
}
```

## Other tools on Jinko MCP (6)

- `trip` — Destructive — https://policylayer.com/tools/com-gojinko-mcp-jinko/trip.md
- `flight_search` — Read — https://policylayer.com/tools/com-gojinko-mcp-jinko/flight-search.md
- `hotel_details` — Read — https://policylayer.com/tools/com-gojinko-mcp-jinko/hotel-details.md
- `hotel_search` — Read — https://policylayer.com/tools/com-gojinko-mcp-jinko/hotel-search.md
- `book` — Write — https://policylayer.com/tools/com-gojinko-mcp-jinko/book.md
- `flight_calendar` — Write — https://policylayer.com/tools/com-gojinko-mcp-jinko/flight-calendar.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-gojinko-mcp-jinko · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gojinko-mcp-jinko