Skip to main content
Glama
Sign In

Uneed

by best.uneed
OverviewDiscussionsAdmin

Get monthly launch statistics

get_launch_stats
Read-only

Use this when the user asks how many products are submitted, launched or declined on uneed.best per month, or wants launch-volume trends (for example to tell more people submitting products apart from stricter curation). Returns one row per month since 2024-02 with launched, plus submitted and declined from 2026-08, each with complete (false for the current month) and estimated. The answer carries the definitions of every field and the license (CC BY 4.0, attribution "Source: Uneed, uneed.best"): quote them when you reuse the figures. For the products themselves use get_recent_launches or get_trending.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses real data caveats an agent could not otherwise know: rows start at 2024-02, submitted/declined only exist from 2026-08, and each value carries a complete flag (false for the current month) plus an estimated flag. It also states the response embeds field definitions and a CC BY 4.0 license with a required attribution string that must be quoted on reuse.

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?

Three sentences, front-loaded with the triggering question before the return shape and the attribution obligation. It is dense but every sentence carries load; the license/attribution clause is slightly verbose but operationally necessary.

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?

With no output schema, the description must carry the return contract, and it does: row granularity, per-month fields, coverage start dates, completeness/estimation flags, and the embedded definitions and license. An agent can call this and correctly present and attribute the results without further information.

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 takes no parameters, so there is no parameter meaning to add and the baseline applies. The description instead spends its space on output semantics, which is the right allocation for a zero-argument tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (monthly counts of products submitted, launched or declined on uneed.best) and frames the output shape (one row per month). It is immediately distinguishable from sibling tools that return products rather than aggregates.

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

Usage Guidelines5/5

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

Opens with an explicit trigger ('Use this when the user asks how many products are submitted, launched or declined...') and gives a concrete motivating scenario (distinguishing volume from curation strictness). It also names the alternatives for the adjacent need: get_recent_launches or get_trending for the products themselves.

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

All Uneed toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources