Skip to main content
Glama

iDevice Buyer's Guide

Release calendar

get_release_calendar
Read-onlyIdempotent

Products not yet on sale, in date order: a release date, an announcement event, or a window shown as written (for example Fall 2026), each with who stated it (Announced by the company, Company event, Reported date, Reported window, iDevice estimate) and how many pre-release reports it has. Defaults to the next 120 days; optional from and to (YYYY-MM-DD, at most one year), category (watches, earbuds, glasses, phones, rings) and company narrow it. Products with no dated or sourced window are counted, not listed. Up to 20 products per call with the total; a category, company or shorter range narrows a longer list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_release_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD. Default 120 days after from; at most 366 days.
fromNoFirst day, YYYY-MM-DD. Default today.
companyNoA company or brand word, e.g. 'apple', 'samsung', 'meta'
categoryNoA category word, e.g. 'watches', 'earbuds', 'glasses', 'phones', 'rings'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a 20-products-per-call cap with a total, the rule that undated products are 'counted, not listed,' and the five attribution labels used to source each window.

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 purpose and scope are front-loaded in the first sentence, followed by defaults, filters and the result cap in a logical order. It is dense and slightly run-on, packing the attribution taxonomy into a parenthetical, but every clause carries substantive information.

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?

With no output schema, the description takes on the burden of explaining return values and does so: per-product date/window, attribution source, pre-release report count, a 20-item cap and the total. It also resolves the edge case of products lacking any dated or sourced window, leaving little an agent would need to guess.

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 description coverage is 100%, with from/to patterns, defaults and the 366-day ceiling already documented, plus example values for company and category. The description restates the date format, the one-year bound and the five category words but adds no syntax or interpretation beyond the schema, so the baseline 3 applies.

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 precise scope: 'Products not yet on sale, in date order,' naming the resource, the ordering, and the inclusion criterion in one clause. It also enumerates what each entry carries (release date, announcement event, window, attribution, report count), so an agent can distinguish this forward-looking calendar from past-oriented siblings like get_release_history without opening the schema.

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 operational guidance: defaults to the next 120 days, and from/to/category/company narrow the result, with the explicit advice that 'a category, company or shorter range narrows a longer list.' It stops short of naming an alternative tool or stating when not to use this one, so it is a 4 rather than a 5.

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.