Sailtix

Search private boat charters

charter_search

Read-onlyIdempotent

Searches private boat and yacht charter packages by departure area, date, guest count, vessel type and trip length, returning price, duration, capacity, inclusions and the operator.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	Requested charter date, YYYY-MM-DD.
`limit`	No
`guests`	No
`location`	No	Departure area, e.g. a city or harbor name.
`vessel_type`	No	Vessel category filter, e.g. speedboat or yacht.
`charter_style`	No	Trip style filter, e.g. reef or trolling.
`duration_type`	No	Trip length, e.g. half_day, full_day, overnight.

Output Schema

TableJSON Schema

Name	Required	Description
`query`	Yes	Parameters the search actually ran with, after resolution.
`total`	No
`results`	Yes
`returned`	Yes

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safe read-only nature, and the description adds useful behavioral context by listing the search dimensions and the return fields (price, duration, capacity, inclusions, operator). It does not contradict the annotations and adds context beyond them.

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, front-loaded sentence with no wasted words. It clearly communicates the core purpose and key capabilities in a compact format.

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?

Given the output schema and annotations, the description is sufficient for a search tool. It captures the main purpose, filters, and return information, but could more explicitly address limit behavior and differentiate from sibling search tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds natural-language meaning for parameters like 'guest count' (guests) and 'trip length' (duration_type), which are not fully described in the schema. Most parameters are referenced, though 'limit' and 'charter_style' are not explicitly mentioned.

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 uses a specific verb ('searches') and a clear resource ('private boat and yacht charter packages'), and explicitly lists the key filtering dimensions. It distinguishes from sibling tools like fishing_search and sailing_search by focusing on general private charters.

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 this tool is for finding boat/yacht charters, and the filters give context. However, it does not explicitly state when to use this tool versus alternatives like fishing_search or sailing_search, nor does it mention any exclusions.

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

All Sailtix tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

The tools are mostly distinct: charter_search, fishing_search, and sailing_search target different travel products, while locations_list is a lookup helper. However, fishing_search is explicitly a subcategory of charter_search, which could cause minor confusion if an agent doesn't read the details.

Naming Consistency5/5

All tool names follow a consistent noun_verb pattern with lowercase and underscores: charter_search, fishing_search, locations_list, sailing_search. The only deviation is the verb 'list' instead of 'search', but the pattern remains predictable and readable.

Tool Count5/5

With four tools, the server is well-scoped for a search-focused maritime travel API. Each tool serves a clear purpose without redundancy or bloat, making it easy for an agent to navigate.

Completeness2/5

The tool surface only covers searching and listing; there are no booking, reservation, or purchase capabilities, which is a significant gap for a service named Sailtix. After finding an option, the agent cannot complete any transaction, leading to dead ends.

Resources

Need Help?