Skip to main content
Glama

Uneed

by best.uneed

Recent launches

get_recent_launches
Read-only

Use this when the user asks what is new or what launched recently. Lists the most recent product launches on uneed.best, newest first, optionally filtered by category (slug or name, see list_categories) and/or tag slug. Ordered strictly by launch date — paid placement is not a factor. Combine with get_trending to know which of them the community voted up.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoTag slug
limitNo
categoryNoCategory slug or exact name (see list_categories)

TDQS

A4.6/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint, destructiveHint), description adds that ordering is by launch date with no paid placement influence, providing useful behavioral context.

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?

Four sentences, all essential, front-loaded with usage instruction. No redundant information.

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

Completeness4/5

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

Covers ordering, filtering, and relation to get_trending. No output schema but description is sufficient for this list tool; minor gap on return format details.

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 has 67% coverage; description adds that category can be slug or exact name and references list_categories, enhancing parameter understanding beyond schema.

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?

Description clearly states 'Lists the most recent product launches on uneed.best, newest first' and distinguishes from sibling tool get_trending by mentioning combination usage.

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?

Explicitly says 'Use this when the user asks what is new or what launched recently' and provides context for filtering and when to combine with get_trending.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

There are two pairs of tools that essentially do the same thing with different output shapes: search/search_products and fetch/get_product. The descriptions try to separate them by use case, but an agent could easily pick the wrong one, making the boundaries unclear.

Naming Consistency3/5

Tool names mix bare verbs (fetch, search) with prefixed verbs (get_, list_) and include a compound form (search_products). While readable, the naming conventions are inconsistent and lack a single predictable pattern.

Tool Count4/5

With 9 tools, the count is reasonable for the domain, but the redundant pairs (search vs search_products, fetch vs get_product) suggest the set is slightly padded and could be consolidated to around 7 tools.

Completeness4/5

The server covers the core read operations for a product directory: search, product details, categories, deals, recent launches, trending, and alternatives. Minor gaps exist, such as no direct category browse without search, but overall the surface is sufficient for the stated purpose.

Resources