Skip to main content
Glama

A1 Synthetic Oil (independent AMSOIL dealer)

Get shopping links

shop_links
Read-onlyIdempotent

AMSOIL product links with dealer referral zo=30734402 for up to 25 product codes, plus the storefront link. The user opens each link, chooses the package size, and checks out on AMSOIL.

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": {
      "codes": "<codes>"
    },
    "name": "shop_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
codesYesU.S. or Canadian product codes.
countryNoStorefront country: US (amsoil.com) or CA (amsoil.ca).US

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: links are attributed to a specific dealer via referral code, capped at 25 codes, and the tool does not transact — the human must open the link, pick a package size, and check out.

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

Conciseness5/5

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

Two tight sentences, front-loaded with what is returned and the cap, then the human-in-the-loop flow. Every clause carries information an agent needs; nothing is padding.

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 carries the return-value burden and does identify the output (product links plus a storefront link). It is slightly silent on the exact return shape (single string vs list per code), which is the only remaining gap for this simple 2-param 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 100%, so 'codes' and 'country' are already documented. The description confirms the 25-item cap and implies a single storefront link tied to the country selection, but adds no format or validation detail beyond the schema; baseline 3 applies.

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?

Specific verb+resource: it produces AMSOIL product purchase links carrying a dealer referral code (zo=30734402) for up to 25 codes, plus the storefront link. This is distinguishable at a glance from get_product (details) and search_products (discovery) among its siblings.

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 only implied through the described user flow ('the user opens each link ... and checks out'). There is no explicit statement of when to prefer this over contact_dealer or get_product, nor any exclusion or prerequisite.

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