Skip to main content
Glama
Sign In
MEME

MEME

by renniyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Discover and rank trends

get_trends

Discovers and ranks developer-culture trends across authorized sources using velocity, engagement, recency, relevance, and cross-platform signals, with confidence scores and freshness indicators.

Instructions

Discovers developer-culture trends from enabled authorized sources (demo source by default; GitHub + Hacker News in live mode) and ranks them by an intelligent composite: velocity, acceleration, engagement quality, recency, developer relevance, cross-platform signals, source diversity and discussion authenticity. Each ranked trend carries a transparent explanation and a confidence score. Results carry honest freshness indicators (live / cached / stale).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
refreshNoForce a fresh collection instead of using the cache
windowHoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: source selection (demo by default, GitHub plus Hacker News in live mode), caching, and freshness labels (live/cached/stale). It does not cover cost, latency, rate limits, or permissions of the collection step, which matter for a tool that may hit external APIs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first clause, which is good. But the sentence balloons into a nine-item ranking-factor list and marketing adjectives like 'intelligent composite' and 'honest freshness indicators' that add length without decision-relevant information.

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?

There is no output schema, so the description usefully explains that each trend carries an explanation, confidence score, and freshness indicator. However, for a tool with three parameters and only 33% schema coverage, the missing explanation of limit and windowHours leaves the definition incomplete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%; only refresh is documented in the schema, and the description mentions caching indirectly through 'cached/stale'. Neither limit nor windowHours is explained anywhere, and the description gives no guidance on sensible ranges or how the ranking interacts with the window.

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?

States a specific verb and resource: discovers developer-culture trends from named sources and ranks them by a composite score. That is clear and actionable. It does not distinguish itself from the singular sibling get_trend, so an agent cannot tell from this text which one to pick.

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?

No when-to-use or when-not-to-use guidance appears; the description only describes operation. It never mentions get_trend as an alternative for a single trend, nor when to set refresh or how windowHours changes scope. The agent is left to infer invocation strategy from the schema alone.

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

Deploy Server

Other Tools