Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

create_marketplace_order_message

Add messages to Discogs marketplace order logs to document communication, update status, and maintain transaction records for music sales.

Instructions

Adds a new message to the order's message log

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYes
messageNo
statusNo

Implementation Reference

  • The MCP tool definition including the execute handler function that creates an order message using MarketplaceService.
    export const createMarketplaceOrderMessageTool: Tool<
      FastMCPSessionAuth,
      typeof OrderCreateMessageParamsSchema
    > = {
      name: 'create_marketplace_order_message',
      description: `Adds a new message to the order's message log`,
      parameters: OrderCreateMessageParamsSchema,
      execute: async (args) => {
        try {
          const marketplaceService = new MarketplaceService();
          const message = await marketplaceService.createOrderMessage(args);
    
          return JSON.stringify(message);
        } catch (error) {
          throw formatDiscogsError(error);
        }
      },
    };
  • Zod schema defining the input parameters for the create_marketplace_order_message tool, extending OrderIdParamSchema with optional message and status.
    export const OrderCreateMessageParamsSchema = OrderIdParamSchema.extend({
      message: z.string().optional(),
      status: OrderStatusSchema.optional(),
    });
  • Registers the createMarketplaceOrderMessageTool with the FastMCP server instance.
    server.addTool(createMarketplaceOrderMessageTool);
  • Calls registerMarketplaceTools which includes the marketplace order message tool registration.
    registerMarketplaceTools(server);
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is a write operation, requires specific permissions, affects order status, or has side effects like notifications, which is insufficient for a mutation tool.

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, making it easy to parse. It's front-loaded with the core action, though brevity contributes to gaps in other dimensions.

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 mutation tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks details on behavior, parameters, and expected outcomes, failing to provide adequate context for safe and effective use.

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?

Schema description coverage is 0%, so the description must compensate but adds no parameter details beyond the tool name. It doesn't explain the 'order_id', 'message', or 'status' parameters, their formats, or relationships, leaving semantics unclear. Baseline 3 as it minimally describes the action.

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 ('Adds') and target resource ('new message to the order's message log'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_marketplace_order_messages' or 'edit_marketplace_order', which reduces specificity.

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 like 'edit_marketplace_order' or 'get_marketplace_order_messages'. The description lacks context about prerequisites, such as whether the order must exist or be in a certain state, leaving usage unclear.

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