Skip to main content
Glama

PebbleLaunch

Launch calendar

get_launch_calendar
Read-only

Seats left per upcoming UTC day (free queue, premium, featured) and the next day with a free seat.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true is consistent with the read-only framing, so no contradiction. Beyond the annotation the description adds what the payload represents (per-day seat counts by tier and the next free day), but says nothing about ordering, rate limits, or whether UTC day boundaries are inclusive — modest added value only.

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?

A single front-loaded sentence with no filler; the parenthetical packs the tier breakdown efficiently. It is arguably too compressed for a tool with two undocumented parameters, but nothing in it is redundant.

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

Completeness3/5

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

For a simple read-only tool with no output schema, the description conveys the rough shape of the result, which is the main thing. The gaps are the two call-shaping parameters and the exact response structure (list of day objects vs. summary), which an agent must guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, so the description carries the full burden and fails: 'days' (a 1-60 window) and 'from' (date string, presumably UTC) are never explained. The mention of 'upcoming UTC day' weakly implies the timezone for 'from' but gives no format or default behavior.

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 names a concrete resource and its returned content: seats left per upcoming UTC day broken down by free queue, premium, and featured tiers, plus the next day with a free seat. That is specific enough to distinguish it from get_launch and list_launches, though it never explicitly contrasts with them.

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 — an agent can infer this is for checking availability over coming days, but there is no statement of when to prefer it over get_launch or list_launches and no mention of prerequisites or how to scope the query. The parenthetical tier list hints at a planning use case rather than stating one.

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