Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

get_marketplace_order

Retrieve details of a specific Discogs marketplace order by providing its order ID to access transaction information.

Instructions

Get a marketplace order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYes

Implementation Reference

  • MCP tool handler (execute function) for 'get_marketplace_order', which delegates to MarketplaceService.getOrder
    export const getMarketplaceOrderTool: Tool<FastMCPSessionAuth, typeof OrderIdParamSchema> = {
      name: 'get_marketplace_order',
      description: 'Get a marketplace order',
      parameters: OrderIdParamSchema,
      execute: async (args) => {
        try {
          const marketplaceService = new MarketplaceService();
          const order = await marketplaceService.getOrder(args);
    
          return JSON.stringify(order);
        } catch (error) {
          throw formatDiscogsError(error);
        }
      },
    };
  • Input parameter schema for the tool: requires 'order_id' as a number.
    export const OrderIdParamSchema = z.object({
      order_id: z.number(),
    });
  • Registration of the getMarketplaceOrderTool with the FastMCP server.
    server.addTool(getMarketplaceOrderTool);
  • Implementation of getOrder in MarketplaceService, performs authenticated API request to Discogs /orders/{order_id} and validates response.
    async getOrder({ order_id }: OrderIdParam): Promise<OrderResponse> {
      try {
        const response = await this.request<OrderResponse>(`/orders/${order_id}`);
    
        const validatedResponse = OrderResponseSchema.parse(response);
        return validatedResponse;
      } catch (error) {
        if (isDiscogsError(error)) {
          throw error;
        }
    
        throw new Error(`Failed to get order: ${String(error)}`);
      }
    }
Behavior1/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 but offers none. It doesn't indicate whether this is a read-only operation, what permissions are required, whether it returns complete order data, or any error conditions. The single word 'get' provides minimal behavioral insight.

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 maximally concise at just three words. While severely under-specified, it contains zero wasted words and is front-loaded with the core action. Every word earns its place, though the place is too small for adequate tool documentation.

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

Completeness1/5

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

For a tool with 1 parameter (0% schema coverage), no annotations, no output schema, and multiple sibling tools in the marketplace domain, this description is completely inadequate. It provides minimal information about what the tool does and nothing about how to use it effectively in context.

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 0% description coverage, meaning the 'order_id' parameter is completely undocumented in the schema. The description adds no parameter information whatsoever - it doesn't explain what format the order_id should be, where to find it, or what constitutes a valid order_id. This fails to compensate for the schema's deficiency.

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

Purpose2/5

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

The description 'Get a marketplace order' is a tautology that essentially restates the tool name without adding meaningful specificity. It uses a generic verb 'get' and doesn't distinguish this tool from sibling tools like 'get_marketplace_orders' (plural) or 'get_marketplace_listing'.

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

Usage Guidelines1/5

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

The description provides absolutely no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, context, or comparison to sibling tools like 'get_marketplace_orders' (which presumably retrieves multiple orders) or 'edit_marketplace_order' (which modifies orders).

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