Skip to main content
Glama

Harris Boat Works - Mercury Repower

search_motors

Read-only

Search current Mercury outboard inventory at Harris Boat Works (Ontario). Filter by horsepower, family (FourStroke, Pro XS, SeaPro, Racing), or stock status. Returns CAD pricing. Excludes Verado. inStock/stockQuantity are the normalized stock signal; availability is the catalog label. candidatePageTruncated warns when more than 500 candidates match: narrow horsepower filters. Decoded fitment needs transom confirmation; specSource flags database rigging presence, and other fields may still be model-code decoded.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_motors"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
familyNo
max_hpNo
min_hpNo
horsepowerNoExact HP (e.g. 90, 150)
in_stock_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/closed-world safety, and the description adds real operational context beyond them: a 500-candidate truncation ceiling with the mitigating action, CAD currency, the Verado exclusion, and the distinction between the normalized inStock signal and the catalog 'availability' label. It stops short of describing pagination behavior or how decoded fitment data should be trusted.

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-loads purpose, then filters, then return-value caveats, with no filler sentences. The final sentence is a dense run-on of cryptic field names (specSource, candidatePageTruncated, decoded fitment) that would read better as separate statements, but overall length is proportionate to the information conveyed.

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

Completeness4/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 necessary work of naming returned fields and their caveats (CAD pricing, inStock vs availability, candidatePageTruncated, decoded fitment needing transom confirmation, specSource). What is missing is any statement about result pagination/limit behavior and how the truncated candidate set interacts with the limit parameter.

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 coverage is only 17% (just the 'horsepower' example), so the description carries the burden and largely fails: 'Filter by horsepower' does not disambiguate the exact-horsepower parameter from min_hp/max_hp ranges, and limit (default 25, max 100) and in_stock_only are never explained. The family list it repeats merely duplicates the enum already in 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?

States a specific verb (Search), resource (current Mercury outboard inventory), and scope (Harris Boat Works, Ontario), plus an explicit exclusion (Verado). An agent can immediately separate this from get_motor (single-record fetch) and from the quote/trade-in siblings 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 Guidelines3/5

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

It names the usable filter axes (horsepower, family, stock status) and gives one operational cue ('narrow horsepower filters' when candidatePageTruncated fires), which implies when the tool is appropriate. However, it never names an alternative tool or states when to prefer get_motor or build_quote instead, so routing is left to inference.

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.