Skip to main content
Glama

iDevice Buyer's Guide

Find products by category and price

find_products
Read-onlyIdempotent

What is on sale in one category (glasses, rings, watches, earbuds, phones, headsets, fitness trackers), optionally at or under a price or from one company, cheapest first. Each carries its current retailer price with the retailer and date, its list price, iDevice's published verdict and the Guide link. Current and previous models are listed; pre-orders and unreleased products are in get_release_calendar. Up to 20 products per call with the total; a price ceiling, company or works_with narrows a longer list.

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": {
      "category": "<category>"
    },
    "name": "find_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyNoA company or brand word, e.g. 'apple', 'samsung', 'meta'
categoryYesglasses, rings, watches, earbuds, phones, headsets or fitness trackers
max_priceNoPrice ceiling in US dollars
works_withNoKeep only products that work with this, e.g. 'iPhone', 'Android' or a device name. Not confirmed counts as unknown, not incompatible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / works_with
      Added value: +{
      +  "description": "Keep only products that work with this, e.g. 'iPhone', 'Android' or a device name. Not confirmed counts as unknown, not incompatible.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, but the description adds real behavioral content beyond them: results are cheapest-first, capped at 20 per call with a total count, and each item carries retailer price, retailer, date, list price, verdict and Guide link. It even explains the semantics of the works_with filter (unconfirmed counts as unknown, not incompatible), which an agent could otherwise misread as exclusion.

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?

Three sentences, front-loaded with the core question and ordering, followed by return shape and then pagination/exclusion notes. The parenthetical category list is bulky but earns its place because the schema declares no enums, so it is the only place the agent can see valid category values.

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

Completeness5/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 must describe returns, and it does: per-product price, retailer, date, list price, verdict and Guide link, plus a cheapest-first ordering and a 20-per-call cap with a total. Combined with the sibling hand-off and filter semantics, nothing essential for a correct first call is missing.

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 description coverage is 100%, so the schema already explains company, category, max_price and works_with, making 3 the baseline. The description adds value by framing max_price/company/works_with as narrowing filters on an otherwise truncated 20-item list, which clarifies their practical role in pagination. It stops short of adding format detail (e.g. company matching rules) beyond what the schema states.

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?

"What is on sale in one category ... cheapest first" states a concrete resource, the enumerated category domain, the default ordering, and the optional narrowing dimensions. It also distinguishes itself from a named sibling (get_release_calendar) that handles pre-orders and unreleased products, so an agent can tell the two apart without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description gives an explicit when-not rule: pre-orders and unreleased products live in get_release_calendar, while current and previous models are returned here. It also tells the agent how to use the optional filters (price ceiling, company, works_with narrow a longer list), which is actionable selection guidance rather than inference.

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.