Skip to main content
Glama

Show yacht details and photos

boat_details
Read-onlyIdempotent

Return yacht details and CDN-backed public URLs for yacht media.

This is the primary tool to call after search_boats whenever the customer asks to see yacht photos, a gallery, plans, videos or documents, or asks about layout, capacity, dimensions, equipment, description, crew or itinerary. When the client supports MCP Apps, render the attached inline Sedna gallery; otherwise display the public URLs returned under media.header, media.photos, media.plans, media.images, media.videos and media.documents. All media in this public tool comes through Sedna's CdnManager; missing CDN media is returned as an empty field and never replaced by a legacy DB URL. id_boat must be copied exactly from search_boats. This tool does not return date-specific prices, extras or availability; use booking_detail for those. Length and beam are optional fleet-supplied facts. When absent they are omitted, never returned as zero or estimated. Do not ask for either value or exclude a yacht unless the customer explicitly requires that dimension.

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": {
      "id_boat": "<id_boat>"
    },
    "name": "boat_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_boatYesExact yacht ID returned by search_boats. Never guess it.
languageNoISO language code supported by Sedna, for example en or fr.en
sheet_typeNobareboat or crewed. Use crewed for crew and itinerary data.bareboat

Output Schema

NameRequiredDescriptionDefault
boatYes
mediaYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • addedOutput schema / properties / boat / properties / bathrooms
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / boat / properties / beam_ft
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / boat / properties / beam_m
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / boat / properties / build_year
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / boat / properties / cabins
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "bunk": {
      +      "type": "integer"
      +    },
      +    "double": {
      +      "type": "integer"
      +    },
      +    "double_berth": {
      +      "type": "integer"
      +    },
      +    "front_peak": {
      +      "type": "integer"
      +    },
      +    "salon": {
      +      "type": "integer"
      +    },
      +    "single": {
      +      "type": "integer"
      +    },
      +    "total": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / boat / properties / crew_capacity
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / boat / properties / deposit
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / boat / properties / flag
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / boat / properties / heads
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / boat / properties / is_crewed
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / boat / properties / length_ft
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / boat / properties / length_m
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / boat / properties / passenger_capacity
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / boat / properties / refit_year
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / boat / properties / sailing_area
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / boat / properties / type
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "boat": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "id": {
      +          "type": "integer"
      +        },
      +        "model": {
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "name",
      +        "model"
      +      ],
      +      "type": "object"
      +    },
      +    "media": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "header": {
      +          "anyOf": [
      +            {
      +              "format": "uri",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "images": {
      +          "items": {
      +            "format": "uri",
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "photos": {
      +          "items": {
      +            "format": "uri",
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "plans": {
      +          "items": {
      +            "format": "uri",
      +            "type": "string"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "header",
      +        "photos",
      +        "plans",
      +        "images"
      +      ],
      +      "type": "object"
      +    },
      +    "schema_version": {
      +      "const": "1.0",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "schema_version",
      +    "boat",
      +    "media"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantive behavior: media is served only via Sedna's CdnManager, missing CDN media is returned as an empty field and never substituted with a legacy DB URL, and length/beam are omitted rather than zeroed or estimated when absent. It also discloses the MCP Apps rendering path versus the plain-URL fallback, which is not inferable from annotations.

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

Conciseness4/5

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

Front-loaded with purpose, then usage, then media/DTO behavior, then exclusions — a logical order with no filler sentences. It loses a little economy by enumerating return field paths (media.header, media.photos, media.plans, etc.) that duplicate the output schema, but the descriptions remain dense with actionable content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only detail tool with an output schema, this covers everything an agent needs: when to call it, what it does not return and where to go instead, how media may be empty, and how to render results with or without MCP Apps. No critical behavior is left to inference.

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 the baseline is 3; all three parameters are already documented in the schema, including the warning that id_boat must never be guessed. The description largely restates that constraint ("id_boat must be copied exactly from search_boats") and only loosely links "crew or itinerary" questions to the crewed sheet type, without naming sheet_type or adding format/semantic detail 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?

Opens with a specific verb+resource ("Return yacht details and CDN-backed public URLs for yacht media") and immediately positions itself relative to siblings as "the primary tool to call after search_boats." An agent can distinguish it from search_boats, compare_boats and booking_detail without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger list (photos, gallery, plans, videos, documents, layout, capacity, dimensions, equipment, description, crew, itinerary) and an explicit routing rule for what it does not cover: "This tool does not return date-specific prices, extras or availability; use booking_detail for those." It also states a prerequisite (call after search_boats) and a negative instruction (do not ask for length/beam unless required).

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