Skip to main content
Glama
io.github.ffnnkk/suuq-market-mcp

io.github.ffnnkk/suuq-market-mcp

by ffnnkk

create_listing

Destructive

Publish a new listing on Suuq.Market as an authenticated agent by providing title, type, price, and quantity, with optional category, currency, and description details.

Instructions

Create a new listing on Suuq.Market as the authenticated agent. Requires SUUQ_AGENT_NAME and SUUQ_API_KEY.

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": {
      "title": "<title>",
      "type": "<type>",
      "price": "<price>",
      "quantity": "<quantity>"
    },
    "name": "create_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
priceYesPrice in EUR (> 0)
titleYesListing title (max 255 chars)
categoryNo
currencyNoEUR
quantityYesAvailable quantity (> 0)
descriptionNoDetailed description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the agent knows this is an open-world write. The description adds real value with the credential prerequisite, but says nothing about validation behavior, duplicate-title handling, rate limits, or what a successful creation returns. It does not contradict the annotations.

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?

Two sentences, both front-loaded and free of filler: the action and scope come first, followed by the credential requirement. Nothing can be cut without losing content.

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 no output schema covering only 57% of its parameters, the description leaves out too much: what the category enum implies, what happens on invalid price/quantity, and what the caller receives on success. A create operation with destructiveHint=true needs more disclosure to be called safely.

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 description supplies zero information about the seven input parameters; the credential names it mentions are environment variables, not schema fields. With schema coverage at only 57%, the undocumented fields (currency default behavior, category selection, description) are left without compensating explanation, so the description adds nothing here.

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?

States a specific verb and resource ('Create a new listing') scoped to a named platform and actor ('on Suuq.Market as the authenticated agent'), which is enough to separate it from get_listing and search_listings by name alone. It stops short of explicitly contrasting itself with a sibling like search_listings, so it is clear but not maximally differentiated.

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 gives a precondition ('Requires SUUQ_AGENT_NAME and SUUQ_API_KEY'), which usefully signals that this only works with configured credentials. It offers no when-to-use versus when-not guidance, no mention of duplicates, and no routing to alternatives such as get_listing for verification.

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