Skip to main content
Glama

Harris Boat Works - Mercury Repower

estimate_trade_in

Read-only

Estimate the trade-in value (CAD) of a customer's current outboard using the live Harris Boat Works valuation. Horsepower may be omitted when the model infers a single validated HP.

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": {
      "brand": "<brand>",
      "year": "<year>"
    },
    "name": "estimate_trade_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
brandYes
modelNo
conditionNo
horsepowerNo
engine_typeNo
engine_hoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / engine_type / enum
      Previous value: -[
      -  "4-stroke",
      -  "2-stroke"
      -]New value: +[
      +  "4-stroke",
      +  "2-stroke",
      +  "proxs",
      +  "optimax",
      +  "etec"
      +]
    • addedInput schema / properties / model
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / year / maximum
      Added value: +2026
    • addedInput schema / properties / year / minimum
      Added value: +1950
    • changedInput schema / properties / year / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / required
      Previous value: -[
      -  "brand",
      -  "year",
      -  "horsepower"
      -]New value: +[
      +  "brand",
      +  "year"
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the result is denominated in CAD, comes from a live valuation service, and has a fallback path when horsepower is missing. It does not describe failure behavior for unrecognized models.

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?

Two sentences, zero waste. The core purpose and currency lead, and the horsepower edge case follows as a secondary clause.

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

Completeness3/5

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

With no output schema, the description does say what comes back (a CAD trade-in value), which is good, and annotations cover the safety profile. However, for a 7-parameter tool at 0% schema coverage, it is not complete enough: an agent still cannot tell how condition, engine_hours, or engine_type affect the estimate or what happens with unknown inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, so the description carries the full explanatory burden and mostly does not. It clarifies only the optionality/inference rule for horsepower and leaves brand, year, model, condition, engine_type, and engine_hours entirely undefined, including what the two enums mean in practice.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Estimate the trade-in value (CAD) of a customer's current outboard') and identifies the valuation source (Harris Boat Works). It is clearly distinguishable from sibling read tools like get_motor, though it never explicitly contrasts with build_quote, the nearest related tool.

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?

The only conditional guidance is 'Horsepower may be omitted when the model infers a single validated HP,' which is usage-relevant but narrow. There is no statement about when an agent should call this instead of build_quote or get_motor, so the selection logic is left implicit.

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.