Skip to main content
Glama

Find gear for a set of devices

find_gear_for_device
Read-onlyIdempotent

Given the devices someone uses (laptops, phones, desktops, monitors), finds verified chargers, carry-on power banks, cables, KVM switches and USB-C docks whose specs cover them. Uses the same rules as the SpecSource /setup tool and returns up to 2 products per kind (10 in total).

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": {
      "devices": "<devices>"
    },
    "name": "find_gear_for_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of text fields (notes, labels, answers). One of: "en" (English), "zh-hant" (Traditional Chinese), "zh-hans" (Simplified Chinese). Default "en". Spec values and model numbers are the same in every language. Example: "zh-hant".en
devicesYesRequired. The devices to cover, 1 to 20, each an object with type and optional preset, watts, resolution and inputs. Example: [{"type": "laptop", "preset": "macbook-pro-16"}, {"type": "phone", "watts": 30}, {"type": "monitor", "resolution": "4k", "inputs": ["USB-C"]}].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / devices / description
      Added value: +"Required. The devices to cover, 1 to 20, each an object with type and optional preset, watts, resolution and inputs. Example: [{\"type\": \"laptop\", \"preset\": \"macbook-pro-16\"}, {\"type\": \"phone\", \"watts\": 30}, {\"type\": \"monitor\", \"resolution\": \"4k\", \"inputs\": [\"USB-C\"]}]."
    • changedInput schema / properties / devices / items / properties / inputs / description
      Previous value: -"For monitors. Default [\"HDMI\"]."New value: +"Optional, monitors only. The video inputs the monitor has, as a list of \"HDMI\", \"DisplayPort\" and \"USB-C\". A USB-C input means the cable must carry video. Default [\"HDMI\"]. Example: [\"HDMI\", \"USB-C\"]."
    • changedInput schema / properties / devices / items / properties / preset / description
      Previous value: -"Known device: macbook-air, macbook-pro-14, macbook-pro-16, windows-laptop-65w, windows-laptop-100w, other-laptop, phone, tablet, other-phone, mac-mini, mac-studio, mini-pc, desktop-tower. Sets watts for laptops and phones."New value: +"Optional. A known device model, which sets its charging watts and whether it is a Mac. One of: \"macbook-air\", \"macbook-pro-14\", \"macbook-pro-16\", \"windows-laptop-65w\", \"windows-laptop-100w\", \"other-laptop\", \"phone\", \"tablet\", \"other-phone\", \"mac-mini\", \"mac-studio\", \"mini-pc\", \"desktop-tower\". Must match type (laptop presets for laptops, and so on). No default. Example: \"macbook-pro-16\" (140W)."
    • changedInput schema / properties / devices / items / properties / resolution / description
      Previous value: -"For monitors. Default 4k."New value: +"Optional, monitors only. Highest resolution the monitor runs at: \"1080p\", \"1440p\", \"4k\" or \"5k\" (5K or more). Default \"4k\". Example: \"1440p\"."
    • addedInput schema / properties / devices / items / properties / type / description
      Added value: +"Required. Kind of device: \"laptop\", \"phone\" (phones and tablets), \"desktop\" or \"monitor\". Laptops and phones are charged; desktops count toward KVM switches; monitors decide KVM switches and docks. Example: \"laptop\"."
    • changedInput schema / properties / devices / items / properties / watts / description
      Previous value: -"Charging watts, for laptops and phones. Overrides the preset."New value: +"Optional for laptops and phones (required if no preset gives a wattage). The charging watts the device can draw, a number from 5 to 240; overrides the preset. Ignored for desktops and monitors. Example: 65."
    • changedInput schema / properties / lang / description
      Previous value: -"Language for text fields: en, zh-hant (Traditional Chinese) or zh-hans (Simplified Chinese)."New value: +"Language of text fields (notes, labels, answers). One of: \"en\" (English), \"zh-hant\" (Traditional Chinese), \"zh-hans\" (Simplified Chinese). Default \"en\". Spec values and model numbers are the same in every language. Example: \"zh-hant\"."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral information beyond that: results are compatibility-verified, capped at 2 products per kind for a maximum of 10, and follow the same rules as SpecSource /setup, which sets expectations about consistency with another tool.

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 sentences, both load-bearing: the first defines the resource and the matching criterion, the second defines result cardinality and rule provenance. The capability list and the result cap are front-loaded 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?

With no output schema, the description correctly supplies the return shape — up to 2 products per kind, 10 total — and states the matching guarantee. Parameters are fully covered by the schema. It could go slightly further on what a result entry contains or what happens when nothing matches, which keeps it off a 5.

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%, with per-field descriptions, enums, ranges and examples for devices, watts, preset, inputs, resolution and lang, so the schema carries the parameter burden. The description only restates the device kinds (laptops, phones, desktops, monitors) and adds no constraints or interaction rules beyond the schema, which matches the baseline of 3.

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?

States a specific verb and resource: it finds verified chargers, power banks, cables, KVM switches and USB-C docks that cover a supplied device set. That is concrete enough to separate it from compare_products or get_product, but it never names a sibling or draws an explicit boundary against 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the input shape — someone's devices in, compatible accessories out — and the reference to the /setup tool hints at the equivalent workflow. There is no explicit when-to-use statement, no when-not-to-use, and no routing to alternatives such as search_products for browsing rather than coverage-matching.

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