Skip to main content
Glama

mkt_search_listings

Read-onlyIdempotent

공개 필드만 반환(상호·시군구·품목·규격·등급·출하기간·희망가). 연락처 없음. 단가 KRW. deliverable_to 에 구매자 시군구(코드 5자리 또는 '경기 구리시')를 주면 그 지역까지 배송 가능한 건만 남기고, 각 건에 delivery 객체를 중첩한다 — status/예상 직선거리(킬로미터·직선)/운임 범위(대한민국 원)/인도원가. 미신고 공급자는 배제하지 않고 '배송 협의'로 함께 남는다. deliverable_to 를 주지 않으면 응답은 종전과 동일하다(스키마 무변경).

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

Input Schema

NameRequiredDescriptionDefault
itemNo
regionNo
deliverable_toNo구매자 시군구 코드 5자리 또는 '경기 구리시' — 배송 가능 건만

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds substantial context: only public fields are returned, contact details are excluded, unit prices are KRW, undeclared suppliers are kept as 'delivery negotiation' rather than excluded, and the nested delivery object's contents (status, straight-line km, freight range in KRW, landed cost) are spelled out. Pagination, result caps, and sorting are still undisclosed, keeping it from a 5.

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 front-loaded with the return contract, then the deliитverable_to behavior, with no filler sentences. The closing note about the schema being unchanged when the parameter is omitted is slightly redundant but still informative for backward compatibility.

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?

With no output schema, the description properly documents return fields and the nested delivery object, which is the right burden to carry. Gaps remain around item/region matching semantics and result limits, but an agent could call this correctly from what is given.

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 only 33%, so the description must compensate; it does well for deliverable_to (5-digit district code or '경기 구리시', plus the effect of nesting a delivery object) but adds nothing about item or region beyond implying they exist. With two of three parameters left semantically undefined, this is a partial compensation rather than a full one.

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 enumerates the public fields returned (business name, district, item, spec, grade, season, asking price) and states the tool is a listing search with an optional delivery-feasibility filter, so the resource and output shape are unmistakable. It never explicitly contrasts itself with siblings such as mkt_search_rfqs or mkt_check_delivery, so it falls short of a 5.

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?

It gives a clear conditional rule for deliverable_to: pass a buyer district to keep only deliverable listings and get a nested delivery object; omit it and behavior is unchanged. However, there is no guidance on when to use this tool instead of mkt_search_rfqs or mkt_check_delivery, and no statement about what item/region filters accept.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources