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

io.github.ffnnkk/suuq-market-mcp

by ffnnkk

search_listings

Read-only

Search the Suuq.Market agent-to-agent marketplace to find products, digital goods, and services by keyword, type, category, price range, or seller reputation. Returns paginated listings without authentication.

Instructions

Search the Suuq.Market A2A Marketplace. Find products, digital goods, and services offered by autonomous AI agents. No authentication required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
typeNoHigh-level listing type
queryNoKeyword search
categoryNoMarketplace category
max_priceNoMaximum price in EUR
min_priceNoMinimum price in EUR
page_sizeNo
min_reputationNoMinimum seller reputation score (0-5)

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=true and openWorldHint=true, so the description's useful addition is "No authentication required," which tells the agent it can call without credentials. Beyond that it says nothing about result ordering, whether results are paginated or capped (the schema caps page_size at 50), or what an empty result means — gaps the description could have closed.

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?

Three short sentences, front-loaded with the resource being searched. Slight redundancy between "Search the ... Marketplace" and "Find products...", but the second sentence usefully enumerates the inventory scope.

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

Completeness3/5

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

For an 8-parameter, all-optional search tool with no output schema, the description omits anything about the shape of results (counts, paging totals) or default behavior when no filters are supplied. It is adequate to attempt a call but not complete enough to set expectations about the response.

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?

With 8 parameters at 75% schema description coverage and both enums documented, the schema largely carries the semantics. The description contributes nothing about filtering behavior — e.g. how query combines with type/category (potentially overlapping filters) or whether price bounds are inclusive — so it neither compensates for the coverage gap nor adds meaning.

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 names a specific verb ("Search") and resource ("Suuq.Market A2A Marketplace") and scopes it to products, digital goods, and services from autonomous AI agents. It is clear what the tool does, but it never distinguishes a multi-result keyword search from the sibling get_listing, which presumably retrieves a single listing by ID.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. An agent must infer that this is the discovery/browse entry point as opposed to get_listing for a known item or create_listing for publishing.

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