Skip to main content
Glama

get_trending_rooms

Retrieve trending WebSim rooms to discover popular community projects and content. Use limit and offset parameters to control results.

Instructions

Get trending WebSim rooms

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of rooms to return (default: 20)
offsetNoNumber of rooms to skip (default: 0)

Implementation Reference

  • The handler function for the 'get_trending_rooms' MCP tool. It extracts optional limit and offset parameters from args, calls the apiClient.getTrendingRooms helper, formats the JSON response with success status and data, and returns it as MCP content.
    handler: async (args) => {
      const { limit = 20, offset = 0 } = args;
      const result = await apiClient.getTrendingRooms(limit, offset);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            success: true,
            data: result,
            message: `Successfully retrieved ${result.items?.length || 0} trending rooms`
          }, null, 2)
        }]
      };
    }
  • The input schema for the get_trending_rooms tool, defining an object with optional 'limit' and 'offset' number parameters, both with defaults.
    inputSchema: {
      type: "object",
      properties: {
        limit: {
          type: "number",
          description: "Number of rooms to return (default: 20)",
          default: 20
        },
        offset: {
          type: "number",
          description: "Number of rooms to skip (default: 0)",
          default: 0
        }
      }
    },
  • server.js:753-785 (registration)
    The full tool registration object added to the 'tools' array. This defines the name, description, inputSchema, and handler for 'get_trending_rooms', which is used by the MCP server's ListTools and CallTool handlers.
    {
      name: "get_trending_rooms",
      description: "Get trending WebSim rooms",
      inputSchema: {
        type: "object",
        properties: {
          limit: {
            type: "number",
            description: "Number of rooms to return (default: 20)",
            default: 20
          },
          offset: {
            type: "number",
            description: "Number of rooms to skip (default: 0)",
            default: 0
          }
        }
      },
      handler: async (args) => {
        const { limit = 20, offset = 0 } = args;
        const result = await apiClient.getTrendingRooms(limit, offset);
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              success: true,
              data: result,
              message: `Successfully retrieved ${result.items?.length || 0} trending rooms`
            }, null, 2)
          }]
        };
      }
    },
  • The helper method in WebSimAPIClient class that constructs the API request to fetch trending rooms from '/api/v1/feed/rooms' endpoint with pagination parameters, used by the tool handler.
    async getTrendingRooms(limit = 20, offset = 0) {
      const params = new URLSearchParams({ limit: limit.toString(), offset: offset.toString() });
      return this.makeRequest(`/api/v1/feed/rooms?${params}`);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get trending WebSim rooms' but doesn't explain what 'trending' means, whether this is a read-only operation, how results are sorted, or any rate limits or authentication needs. This leaves significant gaps in understanding the tool's behavior.

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?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy to scan and understand quickly without unnecessary elaboration.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'trending' entails, the return format, or any behavioral traits like pagination or sorting. For a tool with no structured metadata, this minimal description leaves too many open questions about how to use it effectively.

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?

The input schema has 100% description coverage, with clear documentation for 'limit' and 'offset' parameters including defaults. The description adds no additional semantic information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without compensating value.

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 'Get trending WebSim rooms' clearly states the verb 'Get' and resource 'trending WebSim rooms', making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_trending_feed' or 'get_posts_feed', which might have overlapping domains but different scopes.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_trending_feed' or 'search_feed' that might serve similar purposes, nor does it specify any prerequisites or contextual cues for selection.

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/gigachadtrey/websimm'

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