Skip to main content
Glama

russia_launches

Retrieve upcoming Russian Roscosmos rocket launches, including Soyuz, Proton, and Angara, and filter results by status or limit.

Instructions

ロシア(Roscosmos)のロケット打ち上げ予定を返す(ソユーズ・プロトン・アンガラ等)。

Args: limit: 返す件数(既定 8、最大 15)。 status: 状態で絞り込み(例 "Go for Launch")。省略で全状態。

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

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.41.4
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / status / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / status / default
      Removed value: -null
    • removedInput schema / properties / status / title
      Removed value: -"Status"
    • addedInput schema / properties / status / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / title
      Removed value: -"russia_launchesArguments"
  2. Addedv0.25.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden; it does add real behavior detail the schema lacks (default 8, hard cap of 15 results, status filter semantics, example value 'Go for Launch'). However it says nothing about read-only nature, data freshness/source, sort order, or what a result record contains.

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 front-loaded sentences plus a compact Args block; every line carries information (purpose, scope, default, cap, filter example). No filler or redundant restatement of the schema.

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 two-parameter read tool this covers purpose, both parameters and their limits, which is most of what an agent needs. It is still thin on return shape and ordering, and with no annotations and no output schema those gaps are not covered elsewhere.

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 description coverage is 0%, so the description must compensate, and it largely does: both parameters are explained, and it supplies the max of 15 and an example status value that the schema does not contain. The status parameter's full value set is only hinted at by one example, not enumerated.

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 a specific verb and resource ('ロシア(Roscosmos)のロケット打ち上げ予定を返す') and scopes it by agency and rocket families (Soyuz, Proton, Angara), which separates it in substance from china_launches / upcoming_launches. It never names those siblings explicitly, so differentiation is implied rather than stated.

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?

The Russian-agency scope implies when to choose this over upcoming_launches or china_launches, but there is no explicit when-to-use/when-not statement or named alternative. The agent must infer routing from the country/agency name alone.

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