Skip to main content
Glama

iDevice Wearables

by io.github.ralphieusa
OverviewDiscussionsAdmin

Get reported claims for a product

get_claims
Read-only

Every well-sourced claim for one product, each with its status (Right, Partly right, Wrong, Never settled, Not comparable, Not checked yet, No outcome yet), how many outlets reported it, who reported it first, and a link to the evidence on idevice.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by claim type, e.g. 'hardware', 'design', 'pricing'
product_slugYesFrom list_products, e.g. 'apple-glasses'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / category
      Added value: +{
+  "description": "Filter by claim type, e.g. 'hardware', 'design', 'pricing'",
+  "type": "string"
+}
    • removedInput schema / properties / confidence
      Removed value: -{
-  "description": "Filter by per-claim confidence tier (7-tier: confirmed, unofficially-confirmed [shown as 'Widely reported'], highly-expected, expected, likely, speculated, pipe-dream).",
-  "enum": [
-    "confirmed",
-    "unofficially-confirmed",
-    "highly-expected",
-    "expected",
-    "likely",
-    "speculated",
-    "pipe-dream"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / product_slug
      Added value: +{
+  "description": "From list_products, e.g. 'apple-glasses'",
+  "type": "string"
+}
    • removedInput schema / properties / slug
      Removed value: -{
-  "description": "Product slug",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "slug"
-]New value: +[
+  "product_slug"
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "results": {
-      "items": {
-        "properties": {
-          "blurb": {
-            "type": "string"
-          },
-          "claim": {
-            "type": "string"
-          },
-          "claim_type": {
-            "type": "string"
-          },
-          "confidence": {
-            "description": "Per-claim confidence tier, 7-tier ladder strongest to weakest. 'unofficially-confirmed' is shown as 'Widely reported' on iDevice.",
-            "enum": [
-              "confirmed",
-              "unofficially-confirmed",
-              "highly-expected",
-              "expected",
-              "likely",
-              "speculated",
-              "pipe-dream"
-            ],
-            "type": "string"
-          },
-          "icon": {
-            "type": "string"
-          },
-          "sort_order": {
-            "type": "number"
-          },
-          "sources": {
-            "items": {
-              "properties": {
-                "name": {
-                  "type": "string"
-                },
-                "tier": {
-                  "type": "string"
-                },
-                "url": {
-                  "type": "string"
-                }
-              },
-              "type": "object"
-            },
-            "type": "array"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "results"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed4 schema fields changed
    • changedInput schema / properties / confidence / description
      Previous value: -"Filter by confidence tier"New value: +"Filter by per-claim confidence tier (7-tier: confirmed, unofficially-confirmed [shown as 'Widely reported'], highly-expected, expected, likely, speculated, pipe-dream)."
    • changedInput schema / properties / confidence / enum
      Previous value: -[
-  "confirmed",
-  "expected",
-  "rumored",
-  "speculative"
-]New value: +[
+  "confirmed",
+  "unofficially-confirmed",
+  "highly-expected",
+  "expected",
+  "likely",
+  "speculated",
+  "pipe-dream"
+]
    • addedOutput schema / properties / results / items / properties / confidence / description
      Added value: +"Per-claim confidence tier, 7-tier ladder strongest to weakest. 'unofficially-confirmed' is shown as 'Widely reported' on iDevice."
    • changedOutput schema / properties / results / items / properties / confidence / enum
      Previous value: -[
-  "confirmed",
-  "expected",
-  "rumored",
-  "speculative"
-]New value: +[
+  "confirmed",
+  "unofficially-confirmed",
+  "highly-expected",
+  "expected",
+  "likely",
+  "speculated",
+  "pipe-dream"
+]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description does not need to restate safety. It adds useful context about the output structure (statuses, counts, first reporter, link), but does not mention any edge cases, pagination, or potential for large responses. Given the annotation coverage, the description adds moderate value without contradictions.

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?

The description is a single, information-dense sentence that front-loads the core purpose and then lists the key output attributes. It is concise and well-structured, though slightly long, but every phrase adds value.

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 read-only tool with two parameters and no output schema, the description sufficiently explains what the tool returns, including statuses, counts, first reporter, and evidence link. It does not cover error cases or empty results, but for the likely simple use case, it is reasonably complete.

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?

Both parameters are fully described in the schema (100% coverage), so the description does not need to explain them further. The schema already covers the purpose of category and product_slug, and the description adds no additional parameter context. The baseline score of 3 is appropriate.

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 clearly states the tool's function: it retrieves every well-sourced claim for a single product, and enumerates the specific data returned (statuses, outlet count, first reporter, evidence link). This specificity distinguishes it from the sibling search_claims, which implies cross-product search capability.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives like search_claims or compare_products. It implies a need for a product_slug, but does not state when a search across products would be more appropriate or when to prefer this over other sibling tools.

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

All iDevice Wearables 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