Skip to main content
Glama

기납범칙금 조회

efine__paid_violation__query

REQUIRES prior efine__session__login call with same account_link_id. 조회만 합니다. 이미 낸 범칙금 목록을 건수, 다음 쪽이 있는지와 함께 돌려줍니다. 납부, 출력, 건별 상세는 제공하지 않습니다. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. 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

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

Input Schema

NameRequiredDescriptionDefault
page_sizeNoOptional. Rows per page as the institution offers them.
page_indexNoOptional. Page number, 1-based.
output_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, and the description corroborates this by warning the call is 'not purely read-only' because it creates an XBOSS job and consumes one token per call, even though the institution's source data is untouched. It further discloses artifact retention (7-day file life, 15-minute download_url), the anonymous recovery_receipt semantics, and idempotency-key behavior. The only blemish is the tension between '조회만 합니다' and the later 'not purely read-only' statement, which are reconciled but read awkwardly.

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 tool-specific content occupies two sentences; the remainder is a long generic block on artifact retention, recovery receipts, and idempotency boilerplate spliced between English and Korean. Prerequisites are correctly front-loaded, but the receipt paragraph in particular is verbose and largely irrelevant to selecting or invoking this specific tool. The mixed-language structure makes scanning harder than necessary.

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 five optional parameters, no output schema, and a moderate read-path, the definition covers prerequisites, return shape (rows plus count plus next-page indicator), side effects, cost, and artifact handling. Since there is no output schema, the brief return-content sentence carries the load adequately, though field-level return structure is only sketched.

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 earns an extra point by elaborating request_idempotency_key semantics that the schema explicitly defers to the description ('see the tool description') — when to generate it, when to reuse versus regenerate, and that provider-specific keys differ. It also clarifies that output_formats produces artifacts[] entries with expiring links. Page-size and page-index semantics are left entirely to 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?

States a specific verb+resource: it returns the list of already-paid penalties (기납범칙금) together with the count and a has-next-page flag. It also scopes out what siblings might imply by declaring that payment, printing, and per-item detail are not offered. It does not explicitly name the unpaid-variant siblings, so differentiation is inferred from the 'already paid' qualifier rather than stated.

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?

Gives a hard prerequisite ('REQUIRES prior efine__session__login call with same account_link_id') and clear exclusions (no payment, no printing, no per-item detail), which effectively routes an agent away from using this for those needs. It also names the follow-up tool xdata__job__result for expired artifact links. It stops short of naming the direct alternative for unpaid violations.

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