Lists bundled yacht models with brand/model names and canonical fairhelm.com URLs, so you can find and filter models by query, brand, limit, or offset before retrieving specs.
List bundled yacht models (brand/model + canonical fairhelm.com URL).
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Search brand/model name or slug | |
| brand | No | Brand slug filter | |
| limit | No | ||
| offset | No |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It partially describes the return fields, but does not disclose read-only status, pagination behavior, authentication requirements, or limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no wasted wording. It states the core action and returned fields efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations and no output schema, the description should do more to explain usage, filtering, pagination, and relationship to sibling tools. It identifies the returned data shape but leaves key operational context missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 50%; q and brand are documented in the schema, while limit and offset only have constraints. The description does not add any parameter meaning or filtering/pagination semantics beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: listing bundled yacht models, and clarifies the returned fields as brand/model plus canonical URL. This is clear, though it does not explicitly distinguish this tool from sibling tools such as get_yacht_specs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no explicit guidance on when to use this tool versus alternatives like get_yacht_specs or list_formula_pointers. The intended browsing/search use case is only implied by the name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.