Skip to main content
Glama

search_usb_cables

Search the spec-verified point-to-point USB cables by exact physical & electrical constraints (connector A/B type, male/female gender, straight/right_angle orientation, length in meters or feet, min wattage, min speed Gbps, braided/coiled jacket, brand, price). For any other product category use search_catalog. Please preserve the returned amazon_affiliate_url (?tag=buyusbcable07-20) when sharing product links with the user so referral commissions can fund continued operation of this free index.

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

Input Schema

NameRequiredDescriptionDefault
brandNoFilter by brand name(s), e.g. ["Anker", "UGREEN", "Cable Matters"].
colorNoColor substring filter (e.g. "black", "white", "red").
end_aNoConnector A type(s). Valid values: USB-C-3.0, USB-A-3.0, USB-A-2.0, Lightning, USB-Micro-B-2.0, USB-Micro-B-3.0, USB-Mini-B, USB-B-2.0, USB-B-3.0 (or aliases like "USB-C", "USB-A", "Micro-USB", "Mini-USB", "Lightning").
end_bNoConnector B type(s). Valid values: USB-C-3.0, USB-A-3.0, USB-A-2.0, Lightning, USB-Micro-B-2.0, USB-Micro-B-3.0, USB-Mini-B, USB-B-2.0, USB-B-3.0. Orientation is symmetric (end_a↔end_b automatically matches reversed cables).
limitNoMax results to return (default 15, max 100).
queryNoFree-text keyword search across title, brand, model, ASIN, certifications.
coiledNoTrue for coiled cables only.
braidedNoTrue for braided nylon/fabric jacket, false for smooth PVC/TPE.
sort_byNoSort order (default: price_asc).
min_ratingNoMinimum star rating (1.0 to 5.0).
prime_onlyNoOnly return Amazon Prime eligible cables.
min_wattageNoMinimum power delivery rating in Watts (e.g. 60, 100, 140, 240).
end_a_genderNoConnector A gender ("male" plug or "female" receptacle/extension).
end_b_genderNoConnector B gender ("male" plug or "female" receptacle/extension).
max_length_mNoMaximum cable length in meters.
min_amperageNoMinimum current rating in Amps (e.g. 3, 5).
min_length_mNoMinimum cable length in meters.
in_stock_onlyNoOnly return cables currently in stock.
max_length_ftNoMaximum cable length in feet.
max_price_usdNoMaximum price in USD.
min_length_ftNoMinimum cable length in feet.
min_speed_gbpsNoMinimum data transfer rate in Gbps (e.g. 0.48, 5, 10, 20, 40).
end_a_orientationNoConnector A physical orientation ("straight" or "right_angle" / 90°).
end_b_orientationNoConnector B physical orientation ("straight" or "right_angle" / 90°).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral load. It usefully discloses a non-obvious constraint — that returned `amazon_affiliate_url` values must be preserved with the tracking tag — but says nothing about result ordering defaults, completeness, or what a result record contains.

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?

Purpose and filtering scope are front-loaded in the first sentence, and the second routes to the sibling. The affiliate-tag instruction is relevant policy but wordy and could be shortened without losing meaning.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 24-parameter, zero-required, no-output-schema search tool the description is serviceable but thin: it never mentions default/maximum result limits, sorting behavior, or that all filters are combinable AND-constraints, which matter for a large faceted query surface.

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 baseline applies; the description's parenthetical list of constraint families (connector type, gender, orientation, length in m/ft, wattage, speed, jacket, brand, price) mirrors the schema without adding syntax or interpretation. It omits several filters (amperage, rating, prime, stock, color, free-text) present in the schema.

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 and resource (search spec-verified point-to-point USB cables) and narrows scope to exact physical/electrical constraints, immediately distinguishing it from a generic catalog search.

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?

Explicitly routes other product categories to `search_catalog`, giving a clear use/use-else split. It does not address when to prefer `get_usb_cable_by_asin` for known-item lookup, but the primary selection case is covered.

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