Skip to main content
Glama
jotraynor

Soulseek MCP Server

by jotraynor

get_status

Check the current connection status to the Soulseek peer-to-peer network for music file sharing.

Instructions

Check the current connection status to the Soulseek network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP CallTool handler for 'get_status': fetches status from soulseekClient and returns formatted text response.
    case 'get_status': {
      const status = soulseekClient.getStatus();
    
      return {
        content: [
          {
            type: 'text',
            text: status.connected
              ? `Connected to Soulseek as: ${status.username}`
              : 'Not connected to Soulseek. Will connect automatically on first search or download.',
          },
        ],
      };
    }
  • Tool schema registration in ListTools response: name, description, and empty input schema for get_status.
    {
      name: 'get_status',
      description: 'Check the current connection status to the Soulseek network.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
  • Core implementation of getStatus() method in SoulseekClientWrapper that returns connection status and username.
    getStatus(): { connected: boolean; username: string | null } {
      return {
        connected: this.connected,
        username: this.connected ? this.username : null,
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't describe what information is returned, format of the status response, whether this operation has side effects, or any authentication/rate limit considerations. For a status-checking tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that communicates the essential purpose without any wasted words. It's appropriately sized for a simple, parameterless tool and front-loads the key information immediately.

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?

For a status-checking tool with no annotations and no output schema, the description is insufficiently complete. It doesn't describe what information is returned (connection state, latency, error details, etc.), making it difficult for an agent to understand what to expect from this operation. The description should compensate for the lack of structured output information.

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?

The tool has zero parameters, and schema description coverage is 100% (though trivial since there are no parameters). The description appropriately doesn't discuss parameters since none exist, which is correct for this tool configuration. Baseline for zero parameters is 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Check') and target resource ('current connection status to the Soulseek network'), making the tool's purpose immediately understandable. It distinguishes itself from sibling tools 'download' and 'search' by focusing on network connectivity rather than file operations or content discovery.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (verifying network connectivity) but doesn't explicitly state when to use this tool versus alternatives or any prerequisites. While the purpose suggests it's for diagnostic/status checking, there's no guidance about when this check is needed versus attempting operations directly.

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/jotraynor/SoulseekMCP'

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