Skip to main content
Glama

Get launch day status

get_launch_day_status
Read-onlyIdempotent

Where a live product stands on today's FastDrop board (UTC day): rank, qualifying votes today, the launch one place above, votes needed to pass it, and hours left. If you manage the product, also your review-queue boost progress.

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": {
      "slug": "<slug>"
    },
    "name": "get_launch_day_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesProduct slug

Output Schema

NameRequiredDescriptionDefault
nameNo
noteNo
slugYes
aboveNo
boostNo
dayEndsAtYes
hoursLeftNo
rankTodayYesNull until the first qualifying vote today
votesTodayYes
rankedTodayNoLaunches with a qualifying vote today
votesToNextRankYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety bar is met without description help. The description genuinely adds beyond them: the snapshot is scoped to the UTC day, the result is time-sensitive ('hours left'), and an extra section (review-queue boost progress) appears conditionally based on whether the caller manages the product. It does not say what happens if the product is not live today, which is the main remaining gap.

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 compact sentences with the core result set front-loaded and the conditional bonus information placed second. Every clause carries information; nothing is redundant filler.

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?

An output schema exists, so explaining return fields is bonus rather than required, and the description does it well. For a one-parameter read tool the definition is nearly complete; the only omission is behavior when the product is not currently on today's board (error vs. empty result).

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% with a single 'slug' parameter already documented in the schema, so the baseline of 3 applies. The description adds only a weak implicit constraint — the slug should refer to a currently live product — with no format or lookup guidance.

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 names the exact resource ('today's FastDrop board, UTC day') and enumerates the specific data points returned: rank, qualifying votes, the launch one place above, votes needed to pass, hours left. This is clearly distinguishable from siblings like get_product (static product details) or list_launches (enumeration), so an agent can route 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 Guidelines3/5

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

Usage is only implied by the phrase 'a live product' and 'today's board' — the agent can infer this applies to currently-launching products only, but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as get_product for non-launching products. No prerequisites or failure conditions are stated.

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