iDevice Wearables

Compare two or three products

compare_products

Read-only

Side-by-side specs for 2 or 3 products, from the same engine as idevice.com/compare. Each cell carries Confirmed/Rumored/Our read and its source outlet and date. Products in different categories are compared on shared structured facts only. Optional specs filters rows by keyword, e.g. ['battery','sleep'].

Input Schema

TableJSON Schema

Name	Required	Description	Default
`specs`	No	Keywords to keep only matching rows
`product_slugs`	Yes	e.g. ['oura-ring-4','samsung-galaxy-ring-1']

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 15, 2026
RemovedJul 31, 2026
Changed8 schema fields changedJul 8, 2026
- removedOutput schema / properties / results / items / properties / confidence / description
```
Removed value: -"Product-level confidence — a coarse 3-tier signal (may be null). Distinct from the per-claim 7-tier confidence in CLAIM_SCHEMA."
```
- removedOutput schema / properties / results / items / properties / confidence / enum
```
Removed value: -[
-  "confirmed",
-  "expected",
-  "rumored",
-  null
-]
```
- changedOutput schema / properties / results / items / properties / confidence / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```
- removedOutput schema / properties / results / items / properties / hook_line
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / results / items / properties / last_content_changed_at
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / results / items / properties / roadmap_path
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / results / items / properties / spec_name
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / results / items / properties / specs
```
Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "type": "object"
+}
```

Changed3 schema fields changedJul 8, 2026

addedOutput schema / properties / results / items / properties / confidence / description

Added value: +"Product-level confidence — a coarse 3-tier signal (may be null). Distinct from the per-claim 7-tier confidence in CLAIM_SCHEMA."

changedOutput schema / properties / results / items / properties / confidence / enum

Previous value: -[
-  "confirmed",
-  "expected",
-  "rumored",
-  "speculative"
-]New value: +[
+  "confirmed",
+  "expected",
+  "rumored",
+  null
+]

changedOutput schema / properties / results / items / properties / confidence / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

First observedJun 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already mark readOnlyHint=true and openWorldHint=false, and the description adds meaningful behavior: each cell carries Confirmed/Rumored/Our read with source outlet and date, and cross-category comparisons are limited to shared structured facts. This adds context beyond the annotations without contradicting them.

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?

Four sentences, each earning its place: purpose, provenance, cross-category behavior, and filter semantics. It is front-loaded with the primary action and contains no filler or redundant restatement.

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?

For a 2-parameter, read-only comparison tool with no output schema, the description covers what the response cells contain, how cross-category comparisons behave, and how `specs` filters results. It does not spell out the full response format, but annotations and schema handle read-only intent and cardinality, leaving only minor gaps.

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 baseline is 3, but the description adds real value by explaining that `specs` filters rows by keyword with an example (['battery','sleep']) and that `product_slugs` can span different categories with shared-facts-only comparison. This goes beyond the schema's minimal field descriptions.

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?

The description opens with a specific verb and resource: 'Side-by-side specs for 2 or 3 products' and ties it to a known engine (idevice.com/compare). It is clearly distinct from single-product or claim-searching siblings like get_product and search_claims.

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 intended use is implied clearly: compare exactly 2 or 3 products. However, it does not explicitly name alternatives or state when not to use it, such as 'for a single product use get_product instead'. The cross-category caveat helps but does not provide full routing guidance.

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

All iDevice Wearables tools Inspect

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

Need Help?