Skip to main content
Glama
Sign In

iDevice Buyer's Guide

by com.idevice
OverviewDiscussionsAdmin

Is today's price a good price

is_good_price
Read-onlyIdempotent

For one product: today's verified retailer price with the day it was read, compared with iDevice's own daily price record of this exact model: the low, median and high over the last 30 days and, once 90 days are covered, the last 90 days, each with its dates; where today sits against them in percent; and a verdict, good_price, normal, wait or not_enough_data, which is iDevice's published Prices verdict for the product. No low is stated under 30 days of checks, and no price is stated without the day it was read.

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": {
      "product_slug": "<product_slug>"
    },
    "name": "is_good_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_slugYesA product_slug, e.g. 'oura-ring-4'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive operation. The description adds meaningful behavioral context beyond that: the data sufficiency threshold ('No low is stated under 30 days of checks'), date provenance ('no price is stated without the day it was read'), and the full verdict taxonomy.

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

Conciseness3/5

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

The content is front-loaded with the core purpose, and most clauses carry useful meaning. However, it is delivered as one very long, dense sentence with semicolons, making it harder to scan than a structured multi-sentence description.

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?

There is no output schema, so the description must explain the return shape itself. It does so thoroughly: current price and read date, 30-day and eventually 90-day low/median/high with dates, percentile position, and the possible verdict values. It also discloses key data sufficiency constraints, leaving little an agent needs to know before calling it.

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% for the single product_slug parameter, including an example. The description reinforces that this is for one exact product model but adds no syntax, naming, or validation detail beyond the schema, so the baseline of 3 applies.

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 operation: fetch one product's current verified retailer price, compare it against iDevice's 30/90-day low/median/high record, and return a verdict. It is clear what resource and result are involved, but it does not explicitly distinguish itself from similar siblings such as get_price_history, check_deal, should_i_buy, or whats_moved.

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 stated purpose, but there is no explicit guidance on when to use this tool versus get_price_history, check_deal, or should_i_buy. It also does not state when not to use it or what prerequisites exist beyond the product slug.

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