Skip to main content
Glama

iDevice Buyer's Guide

by com.idevice
OverviewDiscussionsAdmin

Find the device that fits

find_best_device
Read-onlyIdempotent

A short ranked list of on-sale products in one category for a shopper: optionally the phone platform they use, a budget, and up to three priorities from the uses iDevice's Guides assign (for example sleep, running, battery-life, photos-video). Each product comes with its verdict (buy_now or wait), its fit with the phone given, today's retailer price, a one-line reason and its sources, and the place its Guide gives a named priority. In the list: a verdict of Buy now or Wait, and Works or Works with limits with the phone given. Order: the verdict, then the fit answer, then where the product's Guide places a named priority among the uses it lists, then price. A priority outside the Guides' uses is refused and the uses are listed. The same list rule as the decision card on idevice.com. No model is involved. For earbuds, when iDevice's earbuds recommendation is published, the order is that recommendation's instead: quality and fit from independent reviewers' findings, card by card (all-around, music and sound, workouts, noise cancellation, calls, value), with the buy-or-wait verdict shown beside each product, where it does not move the product; the answer adds a recommendation block naming each card's pick, strong choices or why there is none, and reads at most two priorities from calls, sound, anc, workouts and comfort. iDevice's own pick answers first, in every category it covers (earbuds, headphones, watches, fitness trackers, glasses, headsets and phones): the product it names for your question, then the alternatives it names, each with its verdict, fit, price and sources, and a best_answer block with the reviews behind the pick. Your phone and budget decide which products fit you, not which is better. Priorities are the uses the pick covers (for example sleep, running, battery life, calls); a use outside them is refused and the uses are listed.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many products, 1 to 5, default 3
categoryYesThe kind of product
budget_usdNoA price ceiling in US dollars
prioritiesNoUp to three uses, e.g. ['sleep','battery-life']. A use iDevice's Guides do not assign is refused, with the list.
owned_platformNoThe phone platform the shopper uses

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "glasses",
-  "rings",
-  "watches",
-  "earbuds",
-  "phones",
-  "headsets",
-  "fitness trackers"
-]New value: +[
+  "glasses",
+  "rings",
+  "watches",
+  "earbuds",
+  "phones",
+  "headsets",
+  "fitness trackers",
+  "headphones"
+]
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral detail beyond annotations: ranking order, no model involvement, refusal of priorities outside the Guides, a special earbuds recommendation ordering when published, and output blocks like best_answer.

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

Conciseness2/5

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

The description is long, rambling, and repetitive, with the priority-refusal rule stated twice and dense special-case rules for earbuds and iDevice picks. It is not front-loaded with the essential behavior, making the most important guidance harder to extract.

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?

There is no output schema, so the description must explain return structure, and it does: verdict, fit, price, one-line reason, sources, priority placement, recommendation blocks, and best_answer. Given the complexity and annotations covering safety, it is mostly complete, though the presentation could be clearer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description nonetheless adds semantic meaning beyond the schema, especially that phone and budget determine which products fit rather than which is better, and that priorities are uses from the Guides with invalid uses refused and the available uses listed.

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 clearly states it returns a short ranked list of on-sale products in one category, with verdicts, fit, price, reasons, sources, and priority placement. It does not explicitly distinguish itself from close siblings like get_best_for, pick_between, or should_i_buy, so it falls short of a 5.

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?

It gives implied usage context: a shopper provides category, optional phone platform, budget, and priorities, and out-of-Guide priorities are refused with the valid uses listed. However, it does not explicitly say when to use this tool versus alternatives such as find_products, get_best_for, or pick_between, and there are no explicit when-not rules.

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

All iDevice Buyer's Guide 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