MCP Booking

booking_sort_results

Sort booking search results by price ascending/descending, rating, distance, or number of reviews to find preferred options quickly.

Instructions

Sort the most recent booking_search results. Options: price_asc, price_desc, rating, distance, 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": {
      "sortBy": "<sortBy>"
    },
    "name": "booking_sort_results"
  }
}

Input Schema

Name	Required	Description	Default
`sortBy`	Yes	Sort criteria: price_asc (cheapest first), price_desc (most expensive first), rating (highest rated), distance (closest to center), reviews (most reviewed)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jun 25, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states sorting action and options, but omits whether results are returned or modified, side effects, or any permissions needed. This is insufficient for full transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence plus a list of options, front-loaded with the core action. Every word is necessary; no filler or repetition. Ideal conciseness for the task.

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?

For a simple sort tool with one parameter and no output schema, the description adequately covers purpose and options. It could mention return value or state change, but given low complexity, it is mostly complete.

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 coverage is 100% with detailed enum descriptions, so baseline is 3. The tool description merely lists the options without adding extra meaning beyond the schema. No additional semantic value is provided.

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 clearly states the tool's action (sort) and resource (most recent booking_search results), which distinguishes it from sibling tools like booking_filter_results that filter but do not sort. The specific verb 'sort' and resource identification leave no ambiguity.

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 description implies usage after booking_search, but provides no explicit guidance on prerequisites, when not to use, or alternatives. For example, it doesn't clarify that it only works on the last search or that it does not filter. Thus, guidance is adequate but incomplete.

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

Deploy Server