SkillFlow MCP Server

get_trending_skills

Discover trending skills on SkillFlow marketplace, sorted by popularity and trust score, to identify in-demand capabilities for AI coding agents.

Instructions

Get currently trending skills on SkillFlow marketplace, sorted by popularity and trust score.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results (default: 5)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 25, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Since annotations are absent, description carries full burden. It discloses sorting behavior (popularity and trust score) and implies time-sensitivity ('currently'), but lacks safety information (read-only status), rate limits, or cache behavior that would be essential for agent decision-making.

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?

Single sentence, front-loaded with action and resource. Zero waste. Every clause earns its place by conveying domain ('SkillFlow marketplace') and behavioral attributes (sorting logic).

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?

Adequate for low complexity (1 optional param, no output schema). Covers essential 'what' and 'how sorted', but gaps remain in usage context (when to browse vs search) given the presence of sibling search_skills.

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% with 'limit' fully described in properties. Per guidelines, baseline is 3 when schema does the heavy lifting. Description does not mention the limit parameter, but no additional semantic context is needed beyond the schema.

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?

Clear specific verb 'Get' and resource 'trending skills'. Mentions 'SkillFlow marketplace' domain and distinguishes from siblings by specifying 'sorted by popularity and trust score' (curated list vs search/query-based retrieval). Could be 5 if it explicitly contrasted with search_skills.

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?

Zero guidance on when to use versus sibling tool search_skills or prerequisites. Does not clarify that this is for discovery/browse without a query, while search_skills requires search terms.

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

Deploy Server