Skip to main content
Glama

거래처 관리 목록 조회

hometax__tax__trade_partner__search_list

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 고객이 관리용으로 등록한 거래처 목록을 조회합니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

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

Input Schema

NameRequiredDescriptionDefault
srt_optNo정렬 방식. '01'=오름차순, '02'=내림차순. 기본 '01'.
txpr_nmNo거래처명으로 거릅니다. 입력하지 않아도 됩니다.
page_numNo쪽 번호. 기본 1.
rprs_fnmNo대표자명으로 거릅니다. 입력하지 않아도 됩니다.
page_sizeNo한 쪽에 받을 건수. 기본 10.
srt_cl_cdNo정렬 기준. '1'=거래처명, '2'=사업자등록번호, '3'=대표자명, '4'=등록일. 기본 '1'.
txpr_dscm_noNo거래처 등록번호로 거릅니다(하이픈을 넣어도 됩니다). 입력하지 않아도 됩니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / page_num / description
      Previous value: -"Page number (default 1)"New value: +"쪽 번호. 기본 1."
    • changedInput schema / properties / page_size / description
      Previous value: -"Page size (default 10)"New value: +"한 쪽에 받을 건수. 기본 10."
    • changedInput schema / properties / rprs_fnm / description
      Previous value: -"Filter by representative name (대표자명). Optional."New value: +"대표자명으로 거릅니다. 입력하지 않아도 됩니다."
    • changedInput schema / properties / srt_cl_cd / description
      Previous value: -"Sort column (정렬 기준): '1'=name(거래처명), '2'=business number, '3'=representative, '4'=registration date. Default '1'."New value: +"정렬 기준. '1'=거래처명, '2'=사업자등록번호, '3'=대표자명, '4'=등록일. 기본 '1'."
    • changedInput schema / properties / srt_opt / description
      Previous value: -"Sort order (정렬 방식): '01'=ascending, '02'=descending. Default '01'."New value: +"정렬 방식. '01'=오름차순, '02'=내림차순. 기본 '01'."
    • changedInput schema / properties / txpr_dscm_no / description
      Previous value: -"Filter by trade partner business number (거래처 등록번호, hyphens ok). Optional."New value: +"거래처 등록번호로 거릅니다(하이픈을 넣어도 됩니다). 입력하지 않아도 됩니다."
    • changedInput schema / properties / txpr_nm / description
      Previous value: -"Filter by trade partner name (거래처명). Optional."New value: +"거래처명으로 거릅니다. 입력하지 않아도 됩니다."
  2. Changed1 schema field changed
    • changedInput schema / properties / request_idempotency_key / description
      Previous value: -"Optional same-request recovery key for authenticated calls; see the tool description."New value: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that each call consumes one token, that a XBOSS job is created and its result stored, and — critically — that despite being a list/search, this call is not purely read-only, which explains and reinforces readOnlyHint=false. The detailed retry semantics for request_idempotency_key (reuse only to recover an unanswered request, new value for new execution) is genuine behavioral context an agent cannot obtain from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loading is decent (prerequisite, then purpose), but the idempotency passage is dense and repetitive ('이 값 없이 다시 부르면 새 요청이 됩니다' restates the prior sentence), and the aside about the separate institutional idempotency_key field is confusing in a description for a different tool. Several sentences could be tightened without losing meaning.

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 9 all-optional parameters fully documented in the schema and no output schema, the description covers what the schema cannot: prerequisite login, side effects, token cost, and retry/idempotency policy. It does not hint at what the returned list contains or how pagination behaves across pages, a minor gap for a paginated list tool.

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 100%, so the baseline is 3; the description earns above that by explaining how to use request_idempotency_key, which the schema itself defers to the description ('쓰는 법은 도구 설명에 있습니다'). It also warns that a similarly named institutional idempotency_key field is a different field and should be left alone, and notes the account_link_id/idempotency interplay for unauthenticated calls, adding real semantic value.

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 second sentence states a specific verb and resource: '고객이 관리용으로 등록한 거래처 목록을 조회합니다' (retrieve the list of trade partners the customer registered for management). That is enough to distinguish it from the invoice/notice/return siblings, which operate on different resources. However, the purpose statement is embedded after a prerequisite line and amid operational boilerplate rather than front-loaded, which slightly weakens the first impression.

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

Usage Guidelines4/5

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

The definition explicitly names the prerequisite tool and the linking field ('먼저 호출할 도구: hometax__session__login (같은 account_link_id)'), and states that unauthenticated trial calls cannot use the optional idempotency field. It does not discuss when to prefer this over any alternative, but no sibling in the catalog covers the same trade-partner resource, so the prerequisite ordering is the main guidance needed and it is present.

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