Skip to main content
Glama

Launchdog (read-only)

Get launch

get_launch
Read-onlyIdempotent

A live or past launch by id (lch_…) or product slug: listing text (untrusted), week, votes, rank.

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

Input Schema

NameRequiredDescriptionDefault
slugNo
launch_idNo

Output Schema

NameRequiredDescriptionDefault
launchYes
next_stepsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / launch / properties / best_for
      Added value: +{
      +  "properties": {
      +    "untrusted_text": {
      +      "type": "string"
      +    }
      +  },
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / launch / properties / platforms
      Added value: +{
      +  "type": "array"
      +}
    • addedOutput schema / properties / launch / properties / pricing_model
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / launch / properties / repo_url
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / launch / properties / works_with
      Added value: +{
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / launch / properties / maker
      Added value: +{
      +  "properties": {
      +    "bio": {
      +      "properties": {
      +        "untrusted_text": {
      +          "type": "string"
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "handle": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "properties": {
      +        "untrusted_text": {
      +          "type": "string"
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "profile_url": {
      +      "type": "string"
      +    }
      +  },
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description still adds real value with 'live or past' (historical records are reachable) and the '(untrusted)' marker on listing text, which is a genuine prompt-injection caution. It stops short of error behavior or lookup-failure semantics.

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?

A single dense fragment with no filler; the lookup keys come first and the returned fields trail as a compact list. The telegraphic style is efficient but slightly elliptical, reading more like a schema note than guidance.

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?

An output schema exists, so enumerating week/votes/rank is redundant but harmless. For a two-optional-parameter lookup the definition is nearly complete, but the zero-coverage schema means the description should have covered parameter interaction and no-match behavior, which it does not.

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 0%, so the description must carry the burden, and it does partially: it assigns 'id (lch_…)' to launch_id with a concrete prefix format and 'product slug' to slug. It says nothing about optionality, mutual exclusivity, or precedence when both are given, which is the main unresolved semantic.

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?

Names the resource (a launch) and the two lookup keys (id `lch_…` or product slug), and the phrase 'live or past' scopes it to both current and historical records. It implicitly separates this single-record fetch from siblings like list_winners and search_board, but never names them, so the differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says to prefer this over search_board for a known id, nor which of the two keys to reach for. With both parameters optional, the agent gets no rule for what happens if neither or both are supplied.

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