Skip to main content
Glama

API Key Safety (education only)

get_quantaira_launch_waves

Read-only

Quantaira's announced Dec 1, 2026 staged launch waves by CoinZoom USDT balance, as posted on its Telegram channel (Nov 13, 2026), with critics link. Guide: https://quantaira.app/api-key-safety-checker#quantaira. No return or profit information.

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

Input Schema

NameRequiredDescriptionDefault
usdtNoOptional planned USDT balance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 genuinely non-obvious context: the data's provenance and date (Telegram, Nov 13, 2026), the presence of a critics link alongside the announcement, and an explicit negative disclosure that no return or profit information is included. It stops short of describing the response shape or whether the data is static snapshot versus live.

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?

One dense sentence front-loads the resource and its date, followed by a short guide URL and a clear limitation. It is efficient, though the phrase 'with critics link' is grammatically awkward and the embedded guide URL is somewhat opaque without explaining what the page contains.

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 read-only, zero-required-parameter lookup with full schema coverage and no output schema, the description covers source, scope, and a key exclusion. The main remaining gap is return structure, which the description only sketches indirectly through 'staged launch waves' and 'critics link'. That is acceptable but not exhaustive.

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 single optional 'usdt' parameter is already documented as an optional planned USDT balance. The description reinforces the CoinZoom-specific framing of that balance, which is a small value-add, but it offers no additional semantics such as how tiers are matched or what happens when the parameter is omitted. Baseline 3 applies when the schema does the heavy lifting.

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 specific resource: Quantaira's Dec 1, 2026 staged launch waves, tiered by CoinZoom USDT balance, sourced from its Telegram channel (Nov 13, 2026), plus a critics link. That is far more concrete than a generic 'get waves'. It does not explicitly distinguish itself from siblings like get_red_flags or get_safe_key_checklist, but the resource is distinct enough that confusion is unlikely.

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 the tool for checking announced launch waves against a planned USDT balance. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative among get_red_flags, get_required_permissions, get_safe_key_checklist, or explain_error. The caveat 'No return or profit information' partially scopes expectations but is not routing guidance.

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.