XBOSS

기납과태료 조회

efine__paid_penalty__query

REQUIRES prior efine__session__login call with same account_link_id. 조회만 합니다. 이미 낸 과태료 목록을 돌려줍니다. all_period 를 true 로 두면 전체 기간을 조회하고, false 로 두면 석 달 이내의 기간(date_from, date_to)을 넣습니다. 납부, 출력, 건별 상세는 제공하지 않습니다. 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

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__paid_penalty__query"
  }
}

Input Schema

Name	Required	Description
`date_to`	No	Optional. Range end as YYYY-MM-DD, at most three months after date_from. YYYYMMDD is rejected.
`date_from`	No	Optional. Range start as YYYY-MM-DD. YYYYMMDD is rejected.
`page_size`	No	Optional. Rows per page as the institution offers them.
`all_period`	Yes	True reads every period. Do not send date_from or date_to with it - a range is rejected.
`page_index`	No	Optional. Page number, 1-based.
`output_formats`	No	선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
`vehicle_number`	No	Optional. Narrows the list to one vehicle.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations declare readOnlyHint=false, and the description explains exactly why: every call consumes one token ('호출마다 토큰 1소진') and creates a server-side XBOSS job whose result is stored, so the call is 'not purely read-only' even though it reads institution data. It additionally discloses artifact lifetime (15-minute download_url, 7-day file retention), recovery_receipt rules for anonymous results, and idempotency_key reuse policy, none of which the annotations convey.

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?

The prerequisite is correctly front-loaded, but a long generic block about artifacts, recovery receipts, and idempotency keys sits between the core purpose and the operationally critical facts (token cost, non-read-only side effect) that appear only at the very end. The bilingual text also mixes terms, forcing the reader to reconcile Korean and English statements of the same rule. Substantial portions read as boilerplate shared across the server rather than content specific to this query.

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 9-parameter tool with no output schema, the description covers login prerequisite, negative scope, artifact delivery and retention, anonymous-result recovery, and idempotency semantics. The one gap is the shape of the returned list itself (fields of a paid-penalty record), which the agent must discover from the response. Everything needed to decide whether and how to call it is present.

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 description coverage is 100%, so every parameter is already documented, including the all_period/date-range exclusion and the three-month cap. The description restates the all_period true/false workflow but adds no format, default, or edge-case detail beyond the schema. The idempotency_key paragraph explains intent but defers back to the description rather than defining usage here, so baseline 3 is appropriate.

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 the list of already-paid penalty notices ('이미 낸 과태료 목록을 돌려줍니다'). It also delimits scope by declaring what it does not do (납부, 출력, 건별 상세), which lets an agent separate it from the unpaid/detail siblings without opening a schema. It stops short of naming the unpaid sibling as the alternative, so it is clear but not fully differentiated.

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 explicit prerequisites ('REQUIRES prior efine__session__login call with same account_link_id') and explicit exclusions for payment, printing, and per-item detail. It also routes the agent to xdata__job__result when a download link has expired. What is missing is a positive pointer for the complementary case (querying unpaid penalties), so the agent must infer that from the sibling list.

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

All XBOSS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?