Skip to main content
Glama

A1 Synthetic Oil (independent AMSOIL dealer)

Search AMSOIL products

search_products
Read-onlyIdempotent

Search the AMSOIL catalog by product name, product code, viscosity grade (for example 5W-30), product type, or category, with the same ranking and typo tolerance as the a1syntheticoil.com catalog search. Returns product codes, the A1 product page, the AMSOIL shopping link with dealer referral zo=30734402, matching categories, and related A1 guides. Does not return prices or stock.

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWhat to look for, for example "0W-20 motor oil", "diesel 15W-40", "ATF", or "EA15K13".
countryNoStorefront country: US (amsoil.com) or CA (amsoil.ca).US
categoryNoOptional category name from list_categories, for example "Diesel oil".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the bar is lower, and the description adds real value on top: result ranking and typo tolerance parity with the site search, plus an explicit negative — no prices or stock data. It does not mention pagination/limit behavior or that results are dealer-referred via zo=30734402's implications, but the added behavioral context is substantive.

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?

Two sentences, front-loaded with purpose and facets before the return-value inventory. Dense but every clause earns its place; the dealer-referral detail is slightly long-winded but relevant to the returned links.

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 correctly carries the burden of describing returns (product codes, product page, shopping link, categories, guides), which is a genuine strength. It stops short of covering result volume/limit semantics, which is the one remaining gap for a 4-parameter search tool.

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 75%, so the schema already documents query, country, and category. The description adds the facet vocabulary for query (name, code, viscosity grade, type, category) and notes ranking/typo tolerance, but says nothing about the limit parameter or the US/CA storefront switch beyond what the schema states.

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 (search) and resource (the AMSOIL catalog) and enumerates the searchable facets — name, code, viscosity, type, category — which cleanly separates it from get_product's single-item lookup and list_categories' browsing. It never explicitly names a sibling, so routing must be inferred from the 'search the whole catalog' framing.

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?

Usage is implied by the facet list and by the exclusion 'Does not return prices or stock', which tells the agent this is not the tool for pricing questions. There is no explicit when-to-use-this-vs-get_product statement or prerequisite guidance (e.g., call list_categories first for the category parameter).

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