Skip to main content
Glama

미납 과태료 조회

efine__unpaid_penalty__query

REQUIRES prior efine__session__login call with same account_link_id. 조회만 합니다. 미납 과태료 목록을 돌려줍니다. all_period 를 true 로 두면 전체 기간을 조회하고, false 로 두면 기간(date_from, date_to)을 넣습니다. date_basis 로 그 기간이 납부기한 기준인지 위반일 기준인지 고릅니다. 납부는 제공하지 않습니다. 파일: 엑셀(xlsx) · 이 작업의 결과로 만든 문서 - output_formats 로 청할 때만 만듭니다. 결과의 artifacts[] 에 실리고, 내려받기 링크(download_url)는 15분 동안 열리며 파일은 7일 동안 보관됩니다. 링크가 만료되면 결과의 job_id 로 xdata__job__result 를 다시 불러 새 링크를 받습니다. 로그인 없이 받은 결과는 함께 온 recovery_receipt 를 따로 보관했다가, 처음의 job_id 나 pack_run_id 와 함께 xdata__job__result 에 보내세요. 증표로는 그 결과 하나만, 원래 파일 보관 기간이 끝날 때까지 열 수 있습니다. 증표는 공개하지 마세요. 잃어버리면 가입해도 되찾을 수 없습니다. 나중에 로그인해도 증표는 그대로 쓰이고, 다른 결과는 열지 못합니다. 증표가 없으면 처음 계정과 같은 환경(데모 · 정식)에서만 결과를 읽을 수 있습니다. For an authenticated call, generate and save request_idempotency_key before the first request. Reuse it with the same arguments only to recover that request after a lost response; use a new key for a new execution. Without it, calling again remains a new request. This optional key is not available to anonymous taste calls. Keep any provider-specific idempotency_key unchanged; it is a different field. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

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": {
      "all_period": "<all_period>"
    },
    "name": "efine__unpaid_penalty__query"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_toNoOptional. Range end as YYYY-MM-DD. YYYYMMDD is rejected.
date_fromNoOptional. Range start as YYYY-MM-DD. YYYYMMDD is rejected.
page_sizeNoOptional. Rows per page on the first page. Pages after the first exist only at 10.
all_periodYesTrue reads every period. Do not send date_from or date_to with it - a range is rejected.
date_basisNoWhat the range means. Optional - defaults to payment_due.
page_indexNoOptional. Page number, 1-based. Pages after the first need all_period true, no vehicle_number, and page_size 10.
output_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
vehicle_numberNoOptional. Narrows the list to one vehicle.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description usefully explains why: each call consumes one token, creates an XBOSS job and stores the result, so it is explicitly not a pure read despite querying the institution. It also discloses the 15-minute download_url lifetime and 7-day artifact retention, which the annotations cannot convey. The remaining mass of text on recovery_receipt handling is exceptional-path detail rather than core behavior of this tool.

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

Conciseness2/5

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

The login precondition is correctly front-loaded, but the body is long, switches between Korean and English mid-paragraph, and repeats the recovery_receipt rule several times (증표 is re-explained across four sentences). The idempotency and missing-token material could be condensed to two lines without losing information.

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 10-parameter tool with no output schema, the definition covers what comes back (list rows, artifacts[], download_url, job_id) and how to re-fetch an expired link. The precondition, cost, and file behavior are all present. Only the anonymous-vs-authenticated split is muddled by length rather than missing.

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, but the description adds meaning by spelling out the mode switch (all_period true = whole period, false = supply date_from/date_to) and by defining what date_basis selects. It also explains that request_idempotency_key is for same-request recovery and must be reused only with identical arguments. It does not restate the page_size/page_index constraints, which live in the schema.

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: it returns a list of unpaid penalties (미납 과태료 목록을 돌려줍니다) and explicitly says payment is not offered (납부는 제공하지 않습니다). That rules out confusion with payment tools. It never names the sibling unpaid_violation / paid_penalty queries, so an agent must infer the distinction from the name alone.

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?

It gives a hard precondition (REQUIRES prior efine__session__login with the same account_link_id) and the selection rule between whole-period and range mode with the date_basis choice. It also states that payment is out of scope, steering the agent elsewhere. It does not name the specific alternative tool for payment or for paid penalties.

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