Skip to main content
Glama

Yachts for sale on YATCO, optionally by builder: name

ecommerce_yatco_yachts
Read-only

Yachts for sale on YATCO (about 6,000 active listings), optionally by builder (e.g. sunseeker, benetti): name, builder, model, year, length, asking price with currency (or price on application), category, staterooms, location, days on market and listing URL, 12 per page, from the public JSON route behind yatco.com search. Values are as the brokers entered them. Usually answers in about 7 s, up to 18 s on slower calls; allow a 30 s timeout. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "ecommerce_yatco_yachts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, 1 to 500 (12 yachts per page, default 1)
builderNoBuilder name, e.g. sunseeker, azimut, benetti (default: all builders)

Output Schema

NameRequiredDescriptionDefault
pageNo
countNo
totalNo
sourceNo
yachtsNo
builderNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond readOnlyHint/openWorldHint by disclosing typical latency (about 7 s, up to 18 s), a recommended 30 s timeout, and the monetization model ($0.002 per successful call via x402 USDC on Base, Solana and 10+ networks, with failed calls free). It also warns that 'values are as the brokers entered them,' a genuine data-quality caveat. It does not describe error responses or what a failed call looks like.

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?

Front-loaded with the resource and scope, then supports in a single field list, then operating details (latency, cost). Dense but every clause carries information an agent needs; no filler sentences.

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?

An output schema exists, so listing return fields is redundant but harmless; the key extras (pagination cap from schema, latency budget, per-call cost, broker-sourced data quality) are all covered. What remains unaddressed is builder matching behavior and failure/empty-result handling for a paid, slow endpoint.

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%, so both parameters are already documented, including the 12-per-page default and the sunseeker/azimut/benetti examples. The description repeats builder examples and page size without adding matching semantics (substring vs exact builder name), so the baseline of 3 applies.

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?

States a specific verb and resource ('Yachts for sale on YATCO'), a concrete scope (about 6,000 active listings), and the optional filter dimension (builder). The colon list enumerates exactly which record fields come back, so an agent knows what it will get before calling.

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 implied rather than stated: the phrase 'optionally by builder' tells the agent the builder filter is discretionary, but there is no explicit when-to-use/when-not framing and no named alternative (none of the listed siblings cover yachts). The latency and timeout note does at least signal this is a slow, network-bound lookup worth batching.

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