ecommerce-mcp-server

manage_wishlist

Add, remove, or view products in your wishlist. Keep track of items you want to purchase.

Instructions

Wunschliste verwalten (hinzufuegen, entfernen, anzeigen).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "manage_wishlist"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	'add', 'remove', oder 'view'
`product_id`	No	Produkt-ID (fuer add/remove)
`product_title`	No	Produktname (fuer add)
`price`	No	Preis (fuer add, optional)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must carry behavioral information. It lists the actions (add, remove, view) but does not mention any side effects, permission requirements, or constraints (e.g., whether the wishlist is user-specific). The basic actions are disclosed, but depth is lacking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, efficiently front-loaded with the purpose. However, structuring it with bullet points or separate sentences for each action could improve readability for an agent.

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?

The description does not explain what the tool returns (despite an output schema existing) or how it integrates with other tools like 'manage_cart'. Given the complexity (4 parameters, multiple actions), more context is needed for complete understanding.

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 coverage is 100%, so the baseline is 3. The description adds no meaning beyond the schema; it merely echoes the parameter categories. No additional context or usage details are provided.

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 verb 'verwalten' (manage) and the resource 'Wunschliste' (wishlist), with the specific actions in parentheses. However, it does not differentiate this tool from the sibling tool 'manage_cart', which also manages a list.

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 'manage_cart' or 'search_products'. The description lacks context on prerequisites, typical use cases, or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server