Skip to main content
Glama

get_trending

Identify trending wish categories and their velocity from the Wishing Well to inform decision-making.

Instructions

Get trending wish categories and velocity from the Wishing Well.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration and handler definition for 'get_trending'.
    // --- Tool: get_trending ---
    server.tool(
      'get_trending',
      'Get trending wish categories and velocity from the Wishing Well.',
      {},
      async () => {
        const trending = queries.getTrending();
        return {
          content: [{ type: 'text', text: JSON.stringify(trending, null, 2) }],
        };
      }
    );
  • Implementation of the 'getTrending' helper function used by the MCP tool.
    function getTrending() {
      const db = getDb();
      const topCategories = db.prepare(
        'SELECT category, COUNT(*) as count FROM wishes GROUP BY category ORDER BY count DESC'
      ).all();
      const thisWeek = db.prepare(
        "SELECT COUNT(*) as count FROM wishes WHERE created_at >= date('now', '-7 days')"
      ).get().count;
      const today = db.prepare(
        "SELECT COUNT(*) as count FROM wishes WHERE created_at >= date('now')"
      ).get().count;
    
      return { top_categories: topCategories, wishes_today: today, wishes_this_week: thisWeek };
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses 'velocity' as a behavioral trait (rate of trending), which adds context beyond the tool name. However, omits mutation safety, auth requirements, caching behavior, or rate limits.

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 efficient sentence with no redundancy. Action verb front-loaded, domain context established immediately, zero wasted words.

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?

Appropriately complete for a zero-parameter tool. Mentions return data types (categories, velocity) compensating for absent output schema. Given low complexity, covers necessary ground despite lacking behavioral depth.

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?

Zero parameters present, which establishes baseline 4 per scoring rules. No parameters exist requiring semantic clarification.

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?

The description uses specific action verb 'Get' with clear resources ('trending wish categories', 'velocity') and domain ('Wishing Well'). It distinguishes from browse_wishes by specifying aggregate trending metrics rather than individual items. However, it lacks specifics on time windows or trending algorithms.

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 guidance provided on when to use this versus browse_wishes or get_leaderboard. No mention of prerequisites, filtering needs, or data freshness requirements.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vinaybhosle/agentstamp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server