Skip to main content
Glama

iDevice Buyer's Guide

Search pre-release reports across all products

search_reports
Read-onlyIdempotent

Find well-sourced pre-release reports by keyword across every covered product, e.g. 'battery', 'display', 'price'. Each result carries its status and product lifecycle. Up to 20 results per call; a more specific keyword narrows a longer list.

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": {
      "query": "<query>"
    },
    "name": "search_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 20, max 20
queryYesKeyword or phrase

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and closed-world behavior, so the description's job is to add context — and it does: results carry status and product lifecycle, and each call returns at most 20 items. It still omits what happens with no matches or whether results are ranked by relevance.

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?

Two sentences, front-loaded with the core action and scope, followed by result-cap and keyword-tuning detail. No filler or repetition of the title.

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 two-parameter read-only search with no output schema, the description supplies what results contain, the result cap, and how to broaden or narrow results. Minor gaps remain around ranking, empty results, and the absence of pagination.

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 goes beyond it by illustrating query values ('battery', 'display', 'price') and explaining that keyword specificity controls list length. It also restates the 20-item cap tied to the limit parameter, though it doesn't explain the minimum length of 2.

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 and resource ('Find ... pre-release reports') plus scope ('by keyword across every covered product'), which clearly separates it from get_reports or get_product. It does not explicitly name any sibling as an alternative, so it stops short of a 5.

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 rather than stated: the reader learns to supply a keyword and that a narrower keyword returns a shorter list, which is query-shaping guidance. There is no explicit when-to-use/when-not-to-use guidance relative to siblings such as get_reports or whats_coming.

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.