Skip to main content
Glama

거래대사 건별 내역 조회

getReconciliationsByFilter

Retrieve reconciliation records filtered by date, status, and transaction details to identify matched, unmatched, or incomparable transactions between merchant and PG records.

Instructions

특정 하위 상점(store)의 거래대사(정산/거래 대사) 건별 내역을 조회합니다.

각 건은 다음 상태 중 하나를 가집니다: MATCHED(대사 성공), NOT_MATCHED(대사 불일치), INCOMPARABLE(대사 불가), NOT_COLLECTED(PG 정보 미수집), POST_CORRECTION(후보정) (내부적으로 구분되는 역방향 대사 불가(backward incomparable)는 INCOMPARABLE 로 합쳐져 제공됩니다.)

대사 불일치 상세는 statuses=[NOT_MATCHED] 로 조회 후 각 건의 notMatchedReasons 를 확인합니다. 대사 불가 사유는 INCOMPARABLE 건의 incomparableReason 필드에서 확인합니다. 날짜는 반드시 YYYY-MM-DD 형식으로 입력하며, dateType 으로 정산일/결제일 기준을 선택합니다. 조회 기간 제약: from 은 최근 6개월 이내여야 하고, 한 번에 조회 가능한 구간은 최대 2주입니다. store 아이디는 list_stores 도구로 먼저 조회할 수 있습니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes조회 종료일 (YYYY-MM-DD)
fromYes조회 시작일 (YYYY-MM-DD)
afterNo이전 페이지의 마지막 커서 (endCursor 값)
firstNo조회할 건 수 (최대 100)
storeNo조회할 하위 상점 아이디. 생략하면 고객사 내 모든 하위 상점을 조회합니다.
pgTxIdNoPG사 거래 아이디 검색
dateTypeNofrom/to 로 제약할 기준 (정산일 / 결제일)TRANSACTION
statusesNo포함할 대사 상태 목록. 불일치 건만 보려면 [NOT_MATCHED] 로 지정합니다.
orderNameNo주문명 검색
paymentIdNo고객사 결제 아이디 검색
actionTypesNo포함할 결제 상태 목록
transactionIdNo포트원 결제 아이디 검색
paymentMethodTypesNo포함할 결제 수단 목록
settlementCurrenciesNo포함할 정산 통화 목록 (세 자리 통화 코드)
transactionCurrenciesNo포함할 결제 통화 목록 (세 자리 통화 코드)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes조회된 거래대사 목록
endCursorYes다음 페이지 조회에 사용할 커서 (after 로 전달)
hasNextPageYes다음 페이지 존재 여부
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses statuses, how to get mismatch details (notMatchedReasons) and incomparable reasons, and the merging of backward incomparable. Missing pagination details (after, first) but overall good.

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?

Description is concise yet informative, with front-loaded purpose and well-organized details. Each sentence adds value; could be slightly tighter but no redundancy.

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?

Covers core functionality, statuses, date constraints, and store lookup. Output schema exists so return format is handled. Missing pagination explanation but overall complete for the tool's complexity.

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 description coverage is 100%, so baseline 3. Description adds meaning by explaining statuses, dateType, and constraints. Adds context like using list_stores to get store ID, which is beyond schema.

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?

The description clearly states the tool retrieves transaction reconciliation details for a specific sub-store. It mentions distinct statuses and differentiates from siblings like getPaymentsByFilter (payments) and getSettlementStatistics (statistics).

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?

Provides clear usage context: date format, query period constraints (last 6 months, max 2 weeks), and suggests using list_stores for store ID. Lacks explicit when-not-to-use alternatives but sufficient for typical use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/portone-io/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server