Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

get_release_community_rating

Retrieve average community rating and vote count for a Discogs music release to assess its reception.

Instructions

Retrieves the release community rating average and count

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
release_idYes

Implementation Reference

  • The main handler for the 'get_release_community_rating' tool. It instantiates ReleaseService and calls getCommunityRating(args), returning the JSON stringified result or formatted error.
    export const getReleaseCommunityRatingTool: Tool<FastMCPSessionAuth, typeof ReleaseIdParamSchema> =
      {
        name: 'get_release_community_rating',
        description: 'Retrieves the release community rating average and count',
        parameters: ReleaseIdParamSchema,
        execute: async (args) => {
          try {
            const releaseService = new ReleaseService();
            const releaseRating = await releaseService.getCommunityRating(args);
    
            return JSON.stringify(releaseRating);
          } catch (error) {
            throw formatDiscogsError(error);
          }
        },
      };
  • Input schema for the tool, defining the required 'release_id' parameter as a positive integer.
    export const ReleaseIdParamSchema = z.object({
      release_id: z.number().min(1, 'The release_id must be non-zero'),
    });
  • Registers the getReleaseCommunityRatingTool (and other database tools) with the FastMCP server.
    export function registerDatabaseTools(server: FastMCP): void {
      server.addTool(getReleaseTool);
      server.addTool(getReleaseRatingTool);
      server.addTool(editReleaseRatingTool);
      server.addTool(deleteReleaseRatingTool);
      server.addTool(getReleaseCommunityRatingTool);
      server.addTool(getMasterReleaseTool);
      server.addTool(getMasterReleaseVersionsTool);
      server.addTool(getArtistTool);
      server.addTool(getArtistReleasesTool);
      server.addTool(getLabelTool);
      server.addTool(getLabelReleasesTool);
      server.addTool(searchTool);
    }
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 the tool retrieves data (implying read-only), but doesn't mention potential constraints like authentication needs, rate limits, or error conditions. For a tool with no annotation coverage, this leaves significant gaps in understanding its 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 that directly states the tool's function without unnecessary words. It's front-loaded with the core action and data, making it easy to parse quickly.

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, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't explain the return format (e.g., structure of the rating data), error handling, or dependencies, leaving the agent with insufficient context for reliable use.

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?

The input schema has 1 parameter with 0% description coverage, and the tool description provides no additional information about the 'release_id' parameter. It doesn't explain what a release ID is, where to find it, or its format, failing to compensate for the schema's lack of documentation.

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 the action ('retrieves') and the specific data ('release community rating average and count'), making the purpose immediately understandable. However, it doesn't distinguish this tool from similar sibling tools like 'get_release_rating_by_user' or 'get_release', which might also involve rating data.

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. With sibling tools like 'get_release_rating_by_user' (likely for individual user ratings) and 'get_release' (possibly broader release info), the description offers no context to help an agent choose appropriately.

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/cswkim/discogs-mcp-server'

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