Skip to main content
Glama
vuvuvu

StreamerSongList MCP Server

by vuvuvu

getStreamerByName

Retrieve a streamer's detailed profile and song request settings to manage their queue and requests.

Instructions

Fetch detailed information about a specific streamer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
streamerNameNoThe name of the streamer

Implementation Reference

  • Primary handler for the 'getStreamerByName' tool in the TypeScript module. Resolves the streamer name via getEffectiveStreamer, calls makeApiRequest to fetch /streamers/{name}, and returns the JSON result.
    case "getStreamerByName": {
      const streamerName = getEffectiveStreamer((args as any)?.streamerName);
      const data = await makeApiRequest(`/streamers/${encodeURIComponent(streamerName)}`);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • JavaScript handler for the 'getStreamerByName' tool. Extracts streamerName from args (falling back to defaultStreamer), fetches from the API, and returns the result or an error message.
    case "getStreamerByName": {
      const { streamerName = defaultStreamer } = args;
    
      if (!streamerName) {
        throw new Error(
          "streamerName is required. Provide a streamerName or set the DEFAULT_STREAMER environment variable."
        );
      }
      
      try {
        const response = await fetch(`${API_BASE}/streamers/${encodeURIComponent(streamerName)}`);
        
        if (!response.ok) {
          return {
            content: [{
              type: "text",
              text: `Error fetching streamer data: ${response.status} ${response.statusText}`
            }]
          };
        }
        
        const streamerData = await response.json();
        return {
          content: [{
            type: "text",
            text: JSON.stringify(streamerData, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: `Error: ${error instanceof Error ? error.message : 'Unknown error'}`
          }]
        };
      }
    }
  • Schema definition for getStreamerByName in TypeScript: defines the inputSchema with an optional 'streamerName' string property.
    {
      name: "getStreamerByName",
      description: "Fetch detailed information about a specific streamer",
      inputSchema: {
        type: "object",
        properties: {
          streamerName: {
            type: "string",
            description: "The name of the streamer",
          },
        },
        required: [],
      },
    },
  • Schema definition for getStreamerByName in JavaScript: defines the inputSchema with an optional 'streamerName' string property.
    {
      name: "getStreamerByName",
      description: "Fetch detailed information about a specific streamer",
      inputSchema: {
        type: "object",
        properties: {
          streamerName: {
            type: "string",
            description: "The name of the streamer",
          },
        },
        required: [],
      },
    },
  • src/index.ts:162-165 (registration)
    Tool registration in TypeScript via server.setRequestHandler(ListToolsRequestSchema), exposing the tools array (which includes getStreamerByName).
    // Register tools
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools,
    }));
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It states 'Fetch detailed information' but does not specify what 'detailed information' includes, any limitations, or that it is a read-only operation. This is adequate but not thorough.

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 description is a single sentence, very concise, but it lacks detail. It is appropriately sized for the complexity but could be more informative.

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?

Given the tool has no output schema and no annotations, the description should clarify the output format or scope. It does not, leaving ambiguity about what 'detailed information' entails. Moderately complete for a simple tool.

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% coverage with parameter 'streamerName' described as 'The name of the streamer'. The description adds no extra meaning beyond the schema, so a baseline of 3 is appropriate.

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 clearly states 'Fetch detailed information about a specific streamer', which is a specific verb+resource. However, it does not differentiate from sibling tools like getQueue or getSongDetails, but the tool name itself is already quite specific.

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 is provided on when to use this tool versus alternatives. There are no mentions of prerequisites, context, or scenarios where this tool is appropriate.

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/vuvuvu/streamersonglist-mcp'

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