Skip to main content
Glama

iDevice Buyer's Guide

Is this price a good deal

check_deal
Read-onlyIdempotent

Whether a price offered for one product is a good deal: GOOD DEAL, NOT A GOOD DEAL or NOT ENOUGH DATA, on the same basis as should_i_buy. Compares the price with the lowest current retailer price iDevice read today, the lowest recent price of this exact model from published prices and iDevice's own checks (said as low_period with its basis, once there is enough price history to name one) and how close the offer is to that lowest price, and gives the buy-or-wait verdict at that price where it can state one. Each line says what it rests on. No probability is given. A line slug (for example 'samsung-galaxy-ring') names the line's newest model; when that model is not on sale the answer is for the newest model of the line that is, and resolved_to says which and why.

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>",
      "price_usd": "<price_usd>"
    },
    "name": "check_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
retailerNoWhere the price was offered, e.g. 'Best Buy'. Repeated in the answer as given.
price_usdYesThe price offered, in US dollars
product_slugYesThe product, a product_slug, e.g. 'oura-ring-4'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

The annotations already establish read-only, idempotent, non-destructive behavior. The description adds substantial context beyond that: it compares against the lowest current retailer price read today, the recent low from published prices and iDevice checks, names low_period with its basis, states that no probability is given, and explains line-slug resolution with resolved_to.

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?

It is front-loaded with the verdict categories, but the long comparison sentence is dense and repetitive, stacking multiple 'lowest' clauses and parentheticals. The line-slug caveat is necessary but also tightly packed, making the description harder to parse than it needs to be.

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 still explains the result categories, per-line basis, low_period, resolved_to, and the no-probability rule. It omits some edge cases such as invalid slug handling, but is largely complete for a read-only price evaluator.

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 adds important meaning for product_slug: a line slug targets the line's newest model, falls back to the newest available model when needed, and reports the choice in resolved_to. It does not add much for price_usd or retailer beyond the schema, keeping it at 4.

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 evaluates whether an offered price for one product is a GOOD DEAL, NOT A GOOD DEAL, or NOT ENOUGH DATA. It references should_i_buy as the same basis, but does not distinguish itself from the similar is_good_price sibling, so it is clear but not fully differentiated.

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?

The description implies when to use it: when you have an offered price for one product and want a deal verdict. It gives no explicit when-not guidance or routing between check_deal, should_i_buy, and is_good_price, so the agent must infer the choice.

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.