Skip to main content
Glama

Get trending launches

toolfound_get_trending
Read-onlyIdempotent

The Toolfound leaderboard: top products launched in the last day, week, or month, ranked by points (community votes plus an AI listing score). Toolfound is a launch platform with a transparent queue, every product here launched publicly on an assigned date and is ownership-verified. Great for 'what launched recently' and 'trending tools' questions.

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": {
      "period": "<period>"
    },
    "name": "toolfound_get_trending"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodYesHow far back to rank launches, counted from now. Short windows show what is hot today, longer windows show sustained winners.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / period / description
      Previous value: -"Leaderboard window: day, week, or month."New value: +"How far back to rank launches, counted from now. Short windows show what is hot today, longer windows show sustained winners."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-redundant context about data provenance — transparent queue, publicly assigned launch dates, ownership-verified listings, and how points are computed. It does not state result count, pagination, or ordering ties, which are the remaining behavioral gaps.

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 resource and scope before the ranking definition and use cases. Slight promotional tint ('transparent queue', 'ownership-verified') is close to filler, but it does convey trust/provenance information an agent may relay to a user.

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?

For a one-parameter, read-only, idempotent list tool with full schema coverage and rich annotations, the description covers purpose, scope, ranking method, and use cases. With no output schema present, the one thing missing is what a result actually looks like (fields, result count, truncation), which would complete it.

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 100% and the enum values are already documented with their own time-window explanation, so the schema carries the parameter burden. The description restates the three windows and adds the ranking basis (points), but contributes no syntax or edge-case detail beyond the schema — baseline 3.

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?

The description names a concrete resource (the Toolfound leaderboard of top launched products) plus the exact scope (last day, week, or month) and the ranking basis (points = community votes plus an AI listing score). That combination clearly separates it from siblings like toolfound_get_verified_board and toolfound_search_tools without needing to name them.

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

Usage Guidelines4/5

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

It gives explicit trigger phrasing: 'Great for "what launched recently" and "trending tools" questions,' which tells an agent exactly which user intents map here. It stops short of naming an alternative or stating when not to use it (e.g., vs. the verified board or launch calendar), so it is clear context rather than full routing.

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