Skip to main content
Glama

Harris Boat Works - Mercury Repower

get_promotions

Read-only

Read promotional offers resolved for one public-catalogue Mercury motor. motorId is required. purchasePath, when sent, must be loose or installed. It is echoed and does not change eligibility or the amount. HBW staff choose what to apply. The current rate, term, minimums and fee come from the live response. Mercury TD Always On is a promotional rate on approved credit (OAC) through DealerPlan, not a standing-rate amortization line, and it ends when this feed stops returning it. This feed does not include standing financing tiers. Compare minimumBeforeTaxCents with the quote's before-tax subtotal after rebates and trade. When minimumAmountFinancedCents is present, compare it with the amount financed, including HST and the DealerPlan fee. Apply your own eligibility checks. Never show a term the program does not offer. Do not reuse a rebate for a different horsepower. Does not apply an offer or write anything.

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": {
      "motorId": "<motorId>"
    },
    "name": "get_promotions"
  }
}

Input Schema

NameRequiredDescriptionDefault
motorIdYesUUID of a public-catalogue Mercury motor
purchasePathNoEchoed only. Does not change eligibility or the amount.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / purchasePath / description
      Previous value: -"Echoed only. Does not change eligibility or rebate."New value: +"Echoed only. Does not change eligibility or the amount."
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world, so safety is covered; the description nonetheless adds real context (the feed excludes standing financing tiers, promo ends when the feed stops returning it, purchasePath is echoed only). Gaps remain: no mention of empty results, expired promos, or error behavior for an invalid motorId. This is useful added context but not a full behavioral picture.

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

Conciseness3/5

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

The purpose and constraints are front-loaded, but the text is a dense run-on that mixes parameter notes, eligibility policy, comparison formulas, and program trivia (TD Always On, DealerPlan) in the same block. Some sentences (the minimumBeforeTaxCents comparison) earn their place; others read as business-rule overflow rather than tool-selection guidance.

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 the right thing by naming key response fields (current rate, term, minimums, fee, minimumBeforeTaxCents, minimumAmountFinancedCents). However, it never enumerates the actual return shape or handles the no-offers case, leaving an agent to discover the payload empirically for a read-only lookup.

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 coverage is 100% and both parameters already document themselves, including the 'Echoed only' note on purchasePath and the enum values. The description restates the required motorId and the loose/installed constraint without adding format, validation, or selection advice beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource: 'Read promotional offers resolved for one public-catalogue Mercury motor', with the motorId requirement spelled out. It is clearly distinct in substance from siblings like get_motor or build_quote, though it never explicitly names or contrasts an alternative.

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?

Gives concrete operating guidance: 'Apply your own eligibility checks', compare minimumBeforeTaxCents against the quote's before-tax subtotal after rebates and trade, and compare minimumAmountFinancedCents with the amount financed including HST and the fee. It also closes off misuse ('Does not apply an offer or write anything'), but never states when to prefer another tool instead.

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.