Skip to main content
Glama

toolfound

by com.toolfound
OverviewDiscussionsAdmin

Get the launch calendar

toolfound_get_launch_calendar

The upcoming Toolfound launch calendar with seat availability per date: featured seats (a scarce, limited number per day) vs how many are already taken, plus 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
horizon_daysNoHow many days ahead to return (default 30, max 180).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that seats are scarce and limited per day, that availability is shown openly with no hidden queues, and that launching is permanently free. It does not address permissions, rate limits, or whether results can go stale, which keeps it from a 5.

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?

Front-loaded with the returned data, then the horizon, then the next-step routing. Most sentences earn their place, though the 'Launching is permanently free / no hidden queues' line leans promotional rather than operational.

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?

For a single-parameter, no-output-schema tool, the description compensates well by spelling out the shape of the returned data (featured vs taken seats, cap, queued count) and the follow-up action. Nothing an agent needs to call this correctly is missing.

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 sole parameter already documents the default (30) and maximum (180). The description repeats the same horizon facts, so it adds no syntax or semantics beyond the schema — the baseline 3 is appropriate.

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 a specific resource (the Toolfound launch calendar) and enumerates exactly what it returns: featured seat availability, taken counts, daily cap, and queued launches. This distinguishes it from siblings like toolfound_get_launch_status and toolfound_submit_product without opening any 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 explicit context ('Use this to pick a launch date before submitting') and names the downstream tool and parameter (toolfound_submit_product with preferred_launch_date). It does not, however, say when NOT to use this versus toolfound_get_launch_status, so it stops short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All toolfound toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources