Skip to main content
Glama

iDevice Buyer's Guide

Report card for a product's pre-release reports

get_report_card
Read-onlyIdempotent

A roll-up of one product's pre-release reports by how they turned out (Right, Partly right, Wrong, Never settled, Not comparable, Not checked yet, No outcome yet), and the reports themselves, newest first: the date, a one-sentence summary, who reported it, the outlet that carried it, its status and a link on idevice.com. Optional query narrows the reports to words in the summary or the outlet.

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": "get_report_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords to look for in the reports, e.g. 'battery' or 'Gurman'
product_slugYesA product_slug, e.g. 'apple-watch'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Words to look for in the records, e.g. 'battery' or 'Gurman'"New value: +"Words to look for in the reports, e.g. 'battery' or 'Gurman'"
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description goes further and discloses behavior the annotations cannot: the outcome taxonomy used for grouping, newest-first ordering, and the exact fields returned per report (date, summary, reporter, outlet, status, link).

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?

One dense sentence front-loads the aggregation (what the tool fundamentally produces) before enumerating returned fields, with the query caveat last. The seven-item outcome list is long but each entry is load-bearing for interpreting the roll-up, and nothing is repeated from the schema.

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 correctly carries the return-shape burden: it names the outcome buckets, per-report fields, ordering, and the link domain. The only soft spot is not making explicit whether the roll-up includes counts/per-bucket numbers, which an agent might reasonably expect from 'roll-up'.

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 real meaning beyond the schema by specifying that the optional query matches words in the report summary or the outlet — a scope detail the schema's 'Words to look for in the reports' leaves ambiguous.

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 verb+resource: a roll-up of one product's pre-release reports grouped by outcome (Right, Partly right, Wrong, etc.), plus the reports themselves. That aggregation framing implicitly sets it apart from the plain-list siblings get_reports/search_reports, but no sibling is named, so an agent still has to infer the distinction.

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 only implied: supplying a product_slug yields that product's report card, and the optional query narrows the underlying reports. There is no explicit when-to-use guidance or comparison against get_reports, search_reports, or get_reviews, which are the closest alternatives an agent must choose between.

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.