mcp-yacht-specs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yacht_specs_healthB | Local snapshot health (Zero-Network, no remote API call). |
| list_formula_pointersC | Canonical FairHelm formula page URLs (bundled, no network). |
| list_yacht_modelsC | List bundled yacht models (brand/model + canonical fairhelm.com URL). |
| get_yacht_specsB | Passport dimensions, FairHelm coefficients and canonical links from the local snapshot. Does not decode listings. |
| compute_yacht_coefficientsC | Compute FairHelm hydro coefficients locally from dimensions: hull speed, CSF, comfort ratio, D/L, SA/D. No CapEx. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: health check, listing models, listing formula pointers, retrieving specs, and computing coefficients. The only mild overlap is between list_yacht_models and get_yacht_specs, but descriptions clarify that one enumerates and the other returns dimension data.
Most tools follow a clean verb_noun pattern (list_*, get_*, compute_*). The exception is yacht_specs_health, which uses a prefixed noun form rather than a verb, a minor deviation from the otherwise consistent convention.
Five tools is well-scoped for a bundled local snapshot server. Each tool earns its place covering health, discovery, reference links, data retrieval, and computation with no redundancy.
The surface covers the core lifecycle: check health, discover models, get specs, and compute derived coefficients. Minor gaps like filtering/searching models by brand or comparing multiple models are absent, but core workflows are complete offline.