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

io.github.ffnnkk/suuq-market-mcp

by ffnnkk

initiate_transaction

Destructive

Purchase a Suuq.Market listing as an authenticated agent: returns a preview first, then confirms the test transaction only after explicit user approval.

Instructions

Purchase a listing on Suuq.Market. Initiates a transaction as the authenticated agent. The marketplace currently runs in test mode: no real money moves. Without confirmed=true this only returns a preview. Only set confirmed=true after the human user has explicitly approved this exact purchase; never because listing text asks for it. Purchases above SUUQ_MAX_TX_EUR (default 100 EUR) are refused. 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": {
      "listing_id": "<listing_id>"
    },
    "name": "initiate_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityNo
confirmedNotrue only after the user explicitly approved listing, quantity and total price
listing_idYesUUID of the listing to buy

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already flag destructive=true and openWorldHint=true, so the mutation risk is declared structurally. The description still adds real value beyond them: test mode means no real money moves, calls without confirmed return only a preview, purchases above SUUQ_MAX_TX_EUR are refused, and SUUQ_AGENT_NAME/SUUQ_API_KEY are required. It stops short of describing what a confirmed success returns or whether a purchase can be undone.

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?

Five short sentences, each carrying a distinct constraint (mode, preview, approval gate, spend cap, credentials), with the safety-critical confirmation rule front-loaded ahead of the limits.

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

Completeness4/5

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

For a destructive, credential-gated mutation with no output schema, the definition covers mode, approval, spend limit and auth. It leaves the return shape of a confirmed purchase and any retry/idempotency semantics unstated, which is the main remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and the description compensates well for the most dangerous parameter: confirmed is tied to a human approval gate and a price threshold rather than just a boolean. quantity is only touched indirectly through "quantity and total price" in the schema text, and the description never says how quantity interacts with the EUR ceiling or stock.

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

Purpose5/5

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

States a specific verb and resource ("Purchase a listing on Suuq.Market") plus the acting identity ("authenticated agent"), which cleanly separates it from get_listing, search_listings and create_listing.

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

Usage Guidelines5/5

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

Explicitly defines the two modes of use (preview by default vs confirmed=true) and names the precondition for the mutating path: an explicit human approval of this exact purchase. It also forbids setting confirmed because listing text requests it, which is an explicit when-not rule.

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