Skip to main content
Glama

Obato

by eu.obato

search_boats

Read-only

Search Obato's public marketplace for boats. Filters: free-text query, category (type_boot), region, brand, price range. English/German/French input is accepted and normalised (e.g. 'sailboat' -> zeilboot, 'Germany' -> land Duitsland); regio may be a Dutch province, a country or a city. Returns up to 25 listings plus an exact total_matches; on 0 results a suggestion with a relaxed filter is included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
merkNoBrand name
limitNo
queryNoFree-text search (title, description, brand)
regioNoDutch province (Friesland, Noord-Holland), a country (Nederland/Netherlands, Duitsland/Germany) or a city/municipality.
prijs_maxNo
prijs_minNo
type_bootNoCategory, e.g. motorboot, zeilboot, sloep. English/German/French terms are accepted (sailboat, motorboat, Segelboot).

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds multi-language normalisation with concrete examples, regio semantics, a listing cap of 25, and a relaxed-filter suggestion on zero results. No contradiction with annotations.

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?

Three tight sentences: purpose, filter list, language/regio caveats, and return shape. Each sentence adds new information and the scoping is front-loaded. No filler.

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?

With seven optional parameters and no output schema, the description clarifies ambiguous regio and type_boot values and states the response shape. It does not mention limit's default or exact output fields, but the schema and annotations cover enough for safe invocation.

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?

Schema description coverage is 57%, but the description compensates: it explains regio accepts province/country/city, type_boot accepts English/German/French terms, query is free-text over title/description/brand, and price range maps to prijs_min/prijs_max. This adds meaning beyond the schema.

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?

Description opens with the specific action and scope: 'Search Obato's public marketplace for boats,' then lists filter dimensions. This distinguishes it from siblings like search_rentals and get_boat_details by marketplace/resource and search-vs-details role.

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?

The description gives clear context for invocation: filters, accepted English/German/French input, regio value types, and return behavior. It does not explicitly name alternatives or state when not to use it, so it stops short of a full score.

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

All Obato toolsInspect
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/5.0
Disambiguation3/5

Most tools target distinct resources, but get_boat_pricing_stats and get_market_stats overlap heavily: both return count, average, median, min/max price scoped by category and region. ask_bo and get_facts also both return cited factual content, leaving some ambiguity even if the descriptions help.

Naming Consistency4/5

The set predominantly follows a verb_noun pattern: search_boats, search_rentals, get_brand_info, compare_brands, and get_boat_details all fit cleanly. market_snapshot breaks the pattern as a bare noun phrase, and ask_bo uses a proper noun, but these are minor deviations within an otherwise predictable convention.

Tool Count5/5

11 tools is well-scoped for a multifaceted read-only marketplace domain covering listings, rentals, brands, marinas, knowledge-graph facts, and market statistics. Each tool earns its place, even though a couple of them partially overlap.

Completeness4/5

Core workflows are covered: boat search and details, rental search, brand lookup and comparison, marina discovery, knowledge-graph facts, and multiple market statistics views. Minor gaps exist, such as no dedicated marina detail endpoint and rental details only appearing via search results, but agents can work around these.

Resources