Skip to main content
Glama

PebbleLaunch

Get one launch

get_launch
Read-only

One launched/scheduled product by slug: details, launch day, votes, rank, and the badge snippet once live.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_launch"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safe-read profile, so the description's job is to add context beyond that. It does add one genuinely useful behavioral detail — the badge snippet appears only 'once live', implying scheduled launches return a partial payload — but it says nothing about behavior for unknown slugs, missing votes/rank on scheduled items, or cost of the call.

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 front-loaded sentence covering identity and return contents with no filler. 'Badge snippet once live' is slightly compressed and could read ambiguously, which keeps it from a 5.

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 one-parameter read tool with no output schema, enumerating the returned fields largely discharges the description's burden. It falls short on edge-case behavior (nonexistent slug, partial data for scheduled launches) that an agent calling with arbitrary slugs would benefit from knowing.

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 description coverage is 0% for the single slug parameter, but the length is constrained (1-60 chars) in structured form. The description clarifies that the slug identifies one launched/scheduled product, which is meaningful context the bare schema lacks, though it gives no format example or guidance on slug derivation.

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 the resource precisely ('One launched/scheduled product by slug') and enumerates the payload contents (details, launch day, votes, rank, badge snippet), which clearly separates it from a plural listing tool. It stops just short of an explicit verb-plus-sibling contrast, so it is clear rather than exemplary.

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 stated when-to-use or when-not-to-use guidance: nothing tells the agent to prefer this over list_launches when browsing, or over check_status when only status is needed. The only implicit signal is that a slug is required, which the schema already conveys.

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