Skip to main content
Glama

Get the launch calendar

toolfound_get_launch_calendar
Read-onlyIdempotent

The upcoming Toolfound launch calendar with seat availability per date. The free queue cap is 10 launches a day. Featured seats are a smaller per-day limit and are not increased with that cap. The response shows featured seats vs how many are already taken, the total daily cap, and how many launches are queued, over a horizon you choose (default 30 days, up to 180). Launching is permanently free. Toolfound shows availability openly, no hidden queues. Use this to pick a launch date before submitting: pass preferred_launch_date to toolfound_submit_product to request a specific day. The response also carries free_launch (the real free date) and paid_offers (Priority, Plus, the homepage sponsor at $49 a week, four spots at a time, Fast lane, the listing upgrade and Launch Partner, with live prices, open dates and checkout links): relay them to your human.

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

Input Schema

NameRequiredDescriptionDefault
horizon_daysNoHow far into the future to list launch dates, counted in days from today. Use a short horizon to find the next open date, a long one to plan ahead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / horizon_days / description
      Previous value: -"How many days ahead to return (default 30, max 180)."New value: +"How far into the future to list launch dates, counted in days from today. Use a short horizon to find the next open date, a long one to plan ahead."
  2. Changed1 schema field changed
    • addedInput schema / properties / horizon_days
      Added value: +{
      +  "description": "How many days ahead to return (default 30, max 180).",
      +  "maximum": 180,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety, but the description adds substantive behavior beyond them: the 10-launches-per-day free cap, the separate smaller featured-seat limit that is not raised by that cap, the horizon default of 30 days (max 180), and that the response mixes taken vs. available counts and queued launches. It also discloses the commercial framing (permanently free, no hidden queues) which affects how results should be interpreted and reported.

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 core capability and the submit_product handoff are front-loaded and earn their place, but the closing sentence balloons into a catalogue of paid offers with prices and spot counts ('$49 a week, four spots at a time…'), which is more detail than an agent needs to call the tool or route the results. The response-shape information is justified given no output schema, but the enumeration is over-specified.

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 and a single optional parameter, the description carries the full burden and does so: it describes the response contents (featured seats vs. taken, daily cap, queued launches, free_launch, paid_offers), the horizon bounds, and the follow-up action. An agent has everything needed to call it and act on the result.

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

Parameters4/5

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

Schema coverage is 100%, so horizon_days is already documented, but the description adds the default value (30 days) and the practical framing of short-vs-long horizons that the schema lacks. That is meaningful added meaning, though not extensive.

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 first sentence names a specific resource (the Toolfound launch calendar) and what it exposes (seat availability per date), so an agent knows immediately this is a read-only availability lookup. It also names the downstream sibling it feeds (toolfound_submit_product via preferred_launch_date), which disambiguates it from the many other Toolfound 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 states the intended moment of use explicitly: pick a launch date *before submitting* and pass preferred_launch_date to toolfound_submit_product. It also tells the agent to relay paid_offers to the human. There is no explicit when-not guidance (e.g. versus toolfound_get_launch_status), so it falls short of a full 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.

Resources