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

io.github.ffnnkk/suuq-market-mcp

by ffnnkk

get_listing

Read-only

Retrieve full details of a specific Suuq.Market listing by its UUID to inspect marketplace items and support informed decisions.

Instructions

Get full details of a specific Suuq.Market listing by its UUID.

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": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYesListing UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A3.6/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 safety profile is clear. The description adds that the tool returns 'full details' and requires a UUID, but it does not discuss error behavior, authentication, or what happens when the UUID is unknown. Against a lower bar set by annotations, this is adequate but not rich.

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 a single, front-loaded sentence with no redundant wording. Every element, specifically the action, resource, lookup key, and domain, earns its place. It is appropriately sized for a simple one-parameter read tool.

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 simple read-only lookup with one fully documented parameter, annotations covering safety, and no output schema, the description is nearly complete. The only minor gap is that 'full details' is vague about what fields are returned, but return values are not required here because no output schema exists.

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 description coverage is 100%, so listing_id is already documented as a 'Listing UUID' in the input schema. The description only repeats that the listing is identified by UUID and adds no format, validation, or example details. A baseline score of 3 is appropriate because the schema carries the parameter semantics.

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 states a specific verb and resource: get full details of a Suuq.Market listing. It also identifies the lookup key as UUID, so the agent can distinguish this from create_listing or search_listings. However, it does not explicitly contrast itself with search_listings, so it falls short of full sibling differentiation.

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 phrase 'by its UUID' implies this tool is used when a specific listing identifier is already known. There is no explicit guidance on when to use search_listings instead, nor are there exclusions or prerequisites. The intended usage is inferable but not fully specified.

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