Skip to main content
Glama

Get launch stats

get_launch_stats
Read-onlyIdempotent

Listings submitted, launched and declined on Neeed Directory per UTC month, oldest first, through the current month, which is marked incomplete. Launched counts the listings of each month that are live now, so every month is marked estimated. The data is CC BY 4.0: show the attribution line with it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
monthsYesOldest first, through the current month
sourceYesThe page that publishes the data
licenseYes
timezoneYes
attributionYesThe credit line to show with the data
definitionsYesWhat each month field counts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / $defs / LaunchMonth / properties / complete / description
      Previous value: -"False for the current month, whose counts still change"New value: +"False for the current month, which is still under way"
    • changedOutput schema / $defs / LaunchMonth / properties / declined / description
      Previous value: -"Listings an admin rejected that month"New value: +"Listings whose rejection that month still stands"
    • changedOutput schema / $defs / LaunchMonth / properties / submitted / description
      Previous value: -"Listings submitted that month"New value: +"Listings submitted that month and still on record"
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavioral details: ordering is oldest first, the current month is incomplete, launched counts reflect listings live now, every month is marked estimated, and output must include attribution. These caveats materially affect interpretation of the results.

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?

The description is three tight sentences: purpose first, then metric semantics and estimation caveats, then the licensing requirement. Every sentence adds useful information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (zero parameters) and has an output schema, so the description need not explain return values. It still supplies the key caveats an agent needs to present the stats correctly, including the incomplete current month, estimated flags, and attribution requirement.

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 has zero parameters and an empty schema, so there is no parameter meaning for the description to add. Baseline 4 applies because no parameter explanation is needed.

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 metric set (listings submitted, launched, and declined) for a specific source (Neeed Directory), grouped per UTC month. It is very clear about what data is returned, though it does not explicitly distinguish itself from any sibling tool.

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 monthly launch-stats scope and the instruction to show the CC BY 4.0 attribution line. However, the description does not state when to use this tool versus alternatives or any exclusions.

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