Skip to main content
Glama

Next launch windows

get_predictions
Read-onlyIdempotent

Predicted next-release windows per flagship family, computed from average historical release cadence. Includes overdue flags.

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_predictions"
  }
}

Input Schema

NameRequiredDescriptionDefault
familyNoOne of: fenix, fr9x, fr-entry, epix, instinct, enduro, edge10x, edgemid, edge-explore, tacx, venu, vivoactive, descent, imini, quatix, marq, approach, hrm, varia, rally, d2, coros-pace, coros-pace-pro, coros-apex, coros-vertix, coros-dura, suunto-9, suunto-race, suunto-vertical, suunto-run, apple-ultra, amazfit-trex, amazfit-trex-ultra, amazfit-cheetah, amazfit-balance, amazfit-gtr, amazfit-gts, amazfit-active, amazfit-pace, amazfit-bip, wahoo-elemnt, wahoo-bolt, wahoo-roam, wahoo-rival, wahoo-ace, wahoo-tickr, wahoo-trackr, wahoo-speedplay, wahoo-kickr, wahoo-kickr-bike, wahoo-kickr-run, polar-vantage, polar-vantage-m, polar-grit, polar-ignite, polar-pacer, polar-sensor, whoop, oura

Output Schema

NameRequiredDescriptionDefault
_viaYesSource attribution for Endurance Wire
methodYesForecast method and uncertainty; dates are unconfirmed
predictionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / family / description
      Previous value: -"One of: fenix, fr9x, fr-entry, epix, instinct, enduro, edge10x, edgemid, venu, vivoactive, descent, imini, quatix, marq, approach, hrm, varia, rally, d2, coros-pace, coros-pace-pro, coros-apex, coros-vertix, suunto-9, suunto-race, suunto-vertical, suunto-run, apple-ultra, amazfit-trex, amazfit-trex-ultra, amazfit-cheetah, amazfit-balance, amazfit-gtr, amazfit-gts, amazfit-active, amazfit-pace, amazfit-bip, wahoo-elemnt, wahoo-bolt, wahoo-roam, wahoo-rival, wahoo-ace, wahoo-tickr, wahoo-trackr, wahoo-speedplay, wahoo-kickr, wahoo-kickr-bike, wahoo-kickr-run, polar-vantage, polar-vantage-m, polar-grit, polar-ignite, polar-pacer, polar-sensor, whoop, oura"New value: +"One of: fenix, fr9x, fr-entry, epix, instinct, enduro, edge10x, edgemid, edge-explore, tacx, venu, vivoactive, descent, imini, quatix, marq, approach, hrm, varia, rally, d2, coros-pace, coros-pace-pro, coros-apex, coros-vertix, coros-dura, suunto-9, suunto-race, suunto-vertical, suunto-run, apple-ultra, amazfit-trex, amazfit-trex-ultra, amazfit-cheetah, amazfit-balance, amazfit-gtr, amazfit-gts, amazfit-active, amazfit-pace, amazfit-bip, wahoo-elemnt, wahoo-bolt, wahoo-roam, wahoo-rival, wahoo-ace, wahoo-tickr, wahoo-trackr, wahoo-speedplay, wahoo-kickr, wahoo-kickr-bike, wahoo-kickr-run, polar-vantage, polar-vantage-m, polar-grit, polar-ignite, polar-pacer, polar-sensor, whoop, oura"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare it read-only, idempotent, and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: values are estimates derived from average historical cadence and may be flagged overdue, telling the agent this is a projection rather than confirmed data.

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 short fragments with zero waste: the core purpose is front-loaded, and the overdue-flag note follows immediately. Nothing could be removed without losing information.

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 an output schema present and annotations covering safety and idempotency, the description only needs to convey methodology and scope, which it does. Minor gaps remain around the forecast horizon and the default behavior when no family is supplied.

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% and the single optional 'family' parameter is fully documented with an explicit enum list, so the description need not repeat it. The phrase 'per flagship family' loosely mirrors the parameter but adds no syntax or default behavior (e.g., what happens when family is omitted).

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?

States a specific verb (predicted) and resource (next-release windows per flagship family) and names the computation basis plus an output feature (overdue flags). This clearly distinguishes it from siblings like get_releases, which list actual releases rather than projections.

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?

The description implies the tool is for forecasting upcoming launches, but never states when to use it over get_releases or get_rumors, nor any exclusions or prerequisites. Usage is inferable from the name and purpose but not spelled out.

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.

Resources