Skip to main content
Glama
Sign In

iDevice Buyer's Guide

by com.idevice
OverviewDiscussionsAdmin

Release window and its odds

release_odds
Read-onlyIdempotent

For one product not yet released: the expected release window, how it is known (announced by the company, a reported window, an iDevice estimate, or the company's release cadence) with how sure iDevice is (Confirmed, Reported or Our read) and who stated it, and the published probability where iDevice publishes one: how often reported windows of that width have held for products later announced, for the window's calendar year and for the window as stated, with the sample size. A window with no recorded basis, or a reported window with no recorded source, is refused (answered: false, refused says why); so is a product already released.

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

Input Schema

NameRequiredDescriptionDefault
product_slugYesA product_slug, e.g. 'apple-glasses'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses important behavior: refusal conditions, the 'answered: false' response shape, the reason field, confidence labels, source attribution, probability definitions, and sample-size context. This gives the agent substantial operational context not covered by annotations.

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?

The description is front-loaded with the core scope and contains no obvious filler, but it is a very long, heavily nested sentence with multiple parentheticals and colon-delimited clauses. It would be easier to parse if split into shorter statements.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return-value burden. It does so thoroughly by explaining the returned release window, basis categories, confidence labels, source, probability, sample size, and refusal behavior.

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?

Schema coverage is 100%, so the single product_slug parameter is already documented by the schema. The description adds the precondition that the product must not yet be released, but it does not add format or validation details beyond the schema example.

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 resource and scope: for one not-yet-released product, it returns the expected release window, basis, confidence, source, and published probability with sample size. It clearly distinguishes anticipated-window data from release history by emphasizing 'not yet released,' though it does not explicitly name sibling tools.

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

Usage Guidelines4/5

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

It gives clear context for use: exactly one product that has not yet been released. It also states when not to use it by saying an already-released product is refused, and it explains data-quality refusals for missing basis or source. It does not name alternative tools such as release history or calendar tools.

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

All iDevice Buyer's Guide 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