Skip to main content
Glama
Sign In

BuyUSBCables Parametric Hardware & Cable Index

by io.github.dwiel
OverviewDiscussionsAdmin

get_product_by_asin

Fetch the full normalized spec record for one Amazon ASIN (or amazon.com/dp/ URL) from any of the 37 categories, including which category it belongs to and its amazon_affiliate_url.

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": {
      "asin": "<asin>"
    },
    "name": "get_product_by_asin"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinYes10-character Amazon ASIN (e.g. "B0CFZPSPBY") or full amazon.com/dp/... URL.
categoryNoOptional hint; the ASIN is still looked up across every category if it is not there.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "usb_cables",
-  "power_cords",
-  "ssds",
-  "memory",
-  "network_switches",
-  "usb_hubs",
-  "wire_terminals",
-  "connectors",
-  "ethernet_cables",
-  "coax_cables",
-  "ac_dc_psus",
-  "dc_dc_converters",
-  "batteries",
-  "cooling_fans",
-  "circuit_breakers",
-  "relays_contactors",
-  "panel_switches",
-  "din_terminal_blocks",
-  "power_meters",
-  "inserts_standoffs",
-  "wire_spools",
-  "motors",
-  "hdmi_cables",
-  "camera_modules",
-  "bearings",
-  "linear_motion",
-  "transmissions",
-  "pumps",
-  "peltier_modules",
-  "heat_shrink_tubing",
-  "heatsinks",
-  "cable_glands",
-  "tubing_hose",
-  "linear_actuators",
-  "solenoid_valves",
-  "proximity_sensors"
-]New value: +[
+  "usb_cables",
+  "power_cords",
+  "ssds",
+  "memory",
+  "network_switches",
+  "usb_hubs",
+  "wire_terminals",
+  "connectors",
+  "ethernet_cables",
+  "coax_cables",
+  "ac_dc_psus",
+  "dc_dc_converters",
+  "batteries",
+  "cooling_fans",
+  "circuit_breakers",
+  "relays_contactors",
+  "panel_switches",
+  "din_terminal_blocks",
+  "power_meters",
+  "inserts_standoffs",
+  "wire_spools",
+  "motors",
+  "hdmi_cables",
+  "camera_modules",
+  "bearings",
+  "linear_motion",
+  "transmissions",
+  "pumps",
+  "peltier_modules",
+  "heat_shrink_tubing",
+  "heatsinks",
+  "cable_glands",
+  "tubing_hose",
+  "linear_actuators",
+  "solenoid_valves",
+  "proximity_sensors",
+  "phones"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "usb_cables",
-  "power_cords",
-  "ssds",
-  "memory",
-  "network_switches",
-  "usb_hubs",
-  "wire_terminals",
-  "connectors",
-  "ethernet_cables",
-  "coax_cables",
-  "ac_dc_psus",
-  "dc_dc_converters",
-  "batteries",
-  "cooling_fans",
-  "circuit_breakers",
-  "relays_contactors",
-  "panel_switches",
-  "din_terminal_blocks",
-  "power_meters",
-  "inserts_standoffs",
-  "wire_spools",
-  "motors",
-  "hdmi_cables",
-  "camera_modules",
-  "bearings",
-  "linear_motion",
-  "transmissions",
-  "pumps",
-  "peltier_modules"
-]New value: +[
+  "usb_cables",
+  "power_cords",
+  "ssds",
+  "memory",
+  "network_switches",
+  "usb_hubs",
+  "wire_terminals",
+  "connectors",
+  "ethernet_cables",
+  "coax_cables",
+  "ac_dc_psus",
+  "dc_dc_converters",
+  "batteries",
+  "cooling_fans",
+  "circuit_breakers",
+  "relays_contactors",
+  "panel_switches",
+  "din_terminal_blocks",
+  "power_meters",
+  "inserts_standoffs",
+  "wire_spools",
+  "motors",
+  "hdmi_cables",
+  "camera_modules",
+  "bearings",
+  "linear_motion",
+  "transmissions",
+  "pumps",
+  "peltier_modules",
+  "heat_shrink_tubing",
+  "heatsinks",
+  "cable_glands",
+  "tubing_hose",
+  "linear_actuators",
+  "solenoid_valves",
+  "proximity_sensors"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "usb_cables",
-  "power_cords",
-  "ssds",
-  "memory",
-  "network_switches",
-  "usb_hubs",
-  "wire_terminals",
-  "connectors",
-  "ethernet_cables",
-  "coax_cables",
-  "ac_dc_psus",
-  "dc_dc_converters",
-  "batteries",
-  "cooling_fans",
-  "circuit_breakers",
-  "relays_contactors",
-  "panel_switches",
-  "din_terminal_blocks",
-  "power_meters",
-  "inserts_standoffs",
-  "wire_spools",
-  "motors",
-  "hdmi_cables",
-  "camera_modules",
-  "bearings",
-  "linear_motion",
-  "transmissions",
-  "pumps"
-]New value: +[
+  "usb_cables",
+  "power_cords",
+  "ssds",
+  "memory",
+  "network_switches",
+  "usb_hubs",
+  "wire_terminals",
+  "connectors",
+  "ethernet_cables",
+  "coax_cables",
+  "ac_dc_psus",
+  "dc_dc_converters",
+  "batteries",
+  "cooling_fans",
+  "circuit_breakers",
+  "relays_contactors",
+  "panel_switches",
+  "din_terminal_blocks",
+  "power_meters",
+  "inserts_standoffs",
+  "wire_spools",
+  "motors",
+  "hdmi_cables",
+  "camera_modules",
+  "bearings",
+  "linear_motion",
+  "transmissions",
+  "pumps",
+  "peltier_modules"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "usb_cables",
-  "power_cords",
-  "ssds",
-  "memory",
-  "network_switches",
-  "usb_hubs",
-  "wire_terminals",
-  "connectors",
-  "ethernet_cables",
-  "coax_cables",
-  "ac_dc_psus",
-  "dc_dc_converters",
-  "batteries",
-  "cooling_fans",
-  "circuit_breakers",
-  "relays_contactors",
-  "panel_switches",
-  "din_terminal_blocks",
-  "power_meters",
-  "inserts_standoffs",
-  "wire_spools",
-  "motors",
-  "hdmi_cables",
-  "camera_modules",
-  "bearings",
-  "linear_motion",
-  "transmissions"
-]New value: +[
+  "usb_cables",
+  "power_cords",
+  "ssds",
+  "memory",
+  "network_switches",
+  "usb_hubs",
+  "wire_terminals",
+  "connectors",
+  "ethernet_cables",
+  "coax_cables",
+  "ac_dc_psus",
+  "dc_dc_converters",
+  "batteries",
+  "cooling_fans",
+  "circuit_breakers",
+  "relays_contactors",
+  "panel_switches",
+  "din_terminal_blocks",
+  "power_meters",
+  "inserts_standoffs",
+  "wire_spools",
+  "motors",
+  "hdmi_cables",
+  "camera_modules",
+  "bearings",
+  "linear_motion",
+  "transmissions",
+  "pumps"
+]
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the disclosure burden and does some of it: it says the record is 'normalized,' spans 37 categories, and includes category membership plus an affiliate URL. It says nothing about what happens when an ASIN is absent from all categories, whether failures return an error or empty result, or any rate/auth constraints — meaningful gaps for a lookup tool with zero annotation coverage.

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?

A single sentence, front-loaded with the verb and resource and tight enough to scan instantly. Every clause (record type, ASIN/URL acceptance, 37-category scope, returned fields) adds information with no 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?

For a two-parameter read tool with a fully described schema and no output schema, the description covers the essentials including a preview of the return shape (which category, affiliate URL). The remaining gap is behavioral: no statement about not-found handling, which matters given there is no output schema to reveal result structure.

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 both the ASIN format (10-character ID or amazon.com/dp/ URL) and the optional category hint are already fully documented in the schema. The description restates the ASIN/URL duality without adding format, validation, or fallback detail beyond what the schema provides, landing at the baseline.

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 states a specific verb and resource: fetching the full normalized spec record for one ASIN, scoped to 'any of the 37 categories,' and names two returned fields (category, amazon_affiliate_url). It implies a breadth contrast with the narrower get_usb_cable_by_asin sibling but never names or compares against it, so the differentiation is inferred rather than stated.

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?

The single-record, all-category scope implies when to reach for this tool over a catalog search, but there is no explicit 'use this when…' or 'use search_catalog instead when…' statement. The most decision-relevant guidance — that the category param is only a hint and the ASIN is looked up across every category — lives in the schema, not the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BuyUSBCables Parametric Hardware & Cable Index toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources