Skip to main content
Glama

A1 Synthetic Oil (independent AMSOIL dealer)

Suggest AMSOIL products for a vehicle

suggest_for_vehicle
Read-onlyIdempotent

Matches the viscosity grade and specification a vehicle's owner's manual lists to AMSOIL products, with shopping links carrying dealer referral zo=30734402 and the official AMSOIL lookup link for confirming the exact fit. It does not look up vehicles: give the requirements from the manual. Without them it returns questions to ask (needs) instead of guessing.

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": {
      "description": "<description>"
    },
    "name": "suggest_for_vehicle"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoStorefront country: US (amsoil.com) or CA (amsoil.ca).US
componentNoWhat is being serviced.engine
viscosityNoViscosity grade from the owner's manual, for example 0W-20.
descriptionYesThe vehicle or machine, for example "2020 Chevy Silverado 5.3L" or "Polaris RZR 1000 transmission". Viscosity and specification may be included here.
vehicle_typeNoOptional; detected from the description when omitted (car = car, SUV, or gasoline light truck).
specificationsNoSpecifications from the owner's manual, for example "API SP, dexos1 Gen 3" or "Dexron VI".
from_owners_manualNoTrue only when the user read the viscosity and specification from the owner's manual.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-open-world), yet the description adds genuinely new behavior: shopping links carry a dealer referral code, an official AMSOIL lookup link is included for confirmation, and missing requirements yield clarifying questions rather than a guess.

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?

Three tight sentences with the core matching behavior front-loaded and the fallback behavior last. The embedded referral code is granular but it is real behavioral information, not filler.

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 steps in to describe both return shapes (products with shopping links vs. clarifying questions). Combined with full schema coverage and a complete annotation set, an agent has enough to call this correctly.

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%, so all seven parameters are already documented, and the description adds only the soft hint that requirements come from the manual and that viscosity/spec may be folded into the description field. Baseline 3 is appropriate when the schema does the heavy lifting.

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+resource: it matches owner's-manual viscosity grade and specification to AMSOIL products and returns shopping links. It also distinguishes itself from vehicle lookup and, implicitly, from sibling catalog tools like get_product and search_products.

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 a clear usage condition and an explicit exclusion: 'It does not look up vehicles: give the requirements from the manual,' plus the fallback behavior when requirements are absent. It stops short of naming the sibling tools an agent might otherwise reach for.

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.

Resources