Skip to main content
Glama

Upcoming AI tool launches

list_upcoming
Read-only

AI tools that are not out yet and launch on a set day (launchAt, UTC), soonest first. Each joins the list on its launch day.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: ordering (soonest first), timezone semantics (UTC), and the inclusion rule that entries join the list on their launch day — useful for interpreting what 'upcoming' means at the boundary.

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 scope and sort order front-loaded and no filler. Every clause carries information about what the list contains or how it is ordered.

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?

For a zero-parameter read-only listing with no output schema, the description covers scope, ordering, and timezone adequately. It stops short of indicating what fields each entry exposes, which would help an agent plan follow-up calls such as get_tool, but the essentials for correct invocation are present.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the schema's empty object. Baseline 4 applies; the mention of launchAt/UTC is a return-value hint rather than a parameter detail.

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?

States the resource precisely: AI tools that are not yet released, with a launch date field (launchAt, UTC), returned soonest-first. An agent can distinguish this from search_tools or list_deals by the 'not out yet' scope, though no sibling is named explicitly.

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 implied by the definition of the set ('not out yet'), so an agent can infer this is for future launches rather than released tools. However, there is no explicit when-to-use/when-not statement and no pointer to search_tools for already-released tools.

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