Skip to main content
Glama

Harris Boat Works - Mercury Repower

get_motor

Read-only

Fetch a single Mercury motor by id or slug, including pricing, decoded shaft/control/start facts, a specSource summary, normalized stock, and deep-link URL. Model-code fitment must be confirmed against the buyer’s transom before ordering; null means not stated. specSource flags database rigging presence; individual fields may still be model-code decoded. inStock/stockQuantity are the normalized stock signal; availability is the catalog label.

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": "get_motor"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoUUID of the motor
slugNoURL slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), yet the description adds substantial semantics: null means 'not stated', specSource flags database rigging presence while fields may still be model-code decoded, and inStock/stockQuantity are the normalized signal versus availability as a catalog label. These are non-obvious data-integrity caveats an agent could not infer.

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-loaded with the fetch statement and payload list, then layered caveats — no filler. It is dense and telegraphic ('specSource flags database rigging presence'), which is efficient but slightly terse for a first read.

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

Completeness5/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 carries the return-value burden and does so by naming every returned element (pricing, decoded shaft/control/start facts, specSource summary, normalized stock, deep-link URL). It also resolves the two most likely data ambiguities (null semantics and stock normalization), which is complete for a single-entity 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 description coverage is 100% for both id (UUID) and slug (URL slug), so the schema already carries the parameter documentation and the baseline is 3. The description restates that both keys are accepted but adds no format, precedence, or fallback rules between them.

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 (Fetch) and resource (a single Mercury motor) and names both lookup keys (id or slug), then enumerates the payload surface (pricing, decoded facts, specSource, stock, deep-link). The word 'single' implicitly distinguishes it from the search_motors sibling, so an agent can route correctly without opening schemas.

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?

Usage is clear from 'Fetch a single ... by id or slug', which signals a direct-lookup call rather than browsing, and it adds a genuine precondition ('Model-code fitment must be confirmed against the buyer's transom before ordering'). It never names search_motors as the alternative when no id/slug is known, so exclusions are absent.

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.