Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

기납과태료 조회

efine__paid_penalty__query
Read-only

REQUIRES prior efine__session__login call with same account_link_id. Read-only. Lists administrative fines already paid. Set all_period true for everything, or false and give a range of at most three months. Paying, printing and per-row detail are not offered. 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소진

Input Schema

NameRequiredDescriptionDefault
date_toNoOptional. Range end as YYYY-MM-DD, at most three months after date_from. YYYYMMDD is rejected.
date_fromNoOptional. Range start as YYYY-MM-DD. YYYYMMDD is rejected.
page_sizeNoOptional. Rows per page as the institution offers them.
all_periodYesTrue reads every period. Do not send date_from or date_to with it - a range is rejected.
page_indexNoOptional. Page number, 1-based.
output_formatsNoOptional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
vehicle_numberNoOptional. Narrows the list to one vehicle.
account_link_idNoAccount link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure).
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / request_idempotency_key
      Added value: +{
+  "description": "Optional same-request recovery key for authenticated calls; see the tool description.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[\\x20-\\x7E]+$",
+  "type": "string"
+}
  2. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations only cover safety (readOnly/destructive), but the description goes well beyond: file retention of 7 days, 15-minute download links, the xdata__job__result refresh path, anonymous recovery_receipt semantics, idempotency-key recovery behavior, and the per-call token cost. This is exactly the value-add context annotations cannot express.

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?

Core purpose, prerequisite, and read-only status are front-loaded well. However, substantial boilerplate about anonymous receipts and idempotency is verbose and partly tangential to this login-gated query, diluting the sections that matter most.

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 no output schema, the description does the work of explaining artifacts[], download_url lifetime, and the job-result refresh path. It does not describe the actual fine-list data fields, but for the file/return mechanism it is largely complete.

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 coverage is 100%, so the schema already documents every parameter precisely, including the three-month range limit and all_period exclusivity. The description largely restates these constraints rather than adding new parameter-level meaning, so baseline 3 applies.

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 and resource ('Lists administrative fines already paid'), which implicitly distinguishes it from the unpaid sibling. It does not explicitly name efine__unpaid_penalty__query or efine__paid_violation__query, so an agent must still reason about which penalty/violation sibling applies.

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?

Strong guidance: requires prior efine__session__login with matching account_link_id, explains the all_period vs date-range fork, and explicitly excludes paying, printing, and per-row detail. It stops short of naming the alternative tools to route to for those excluded actions.

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

All XBOSS toolsInspect
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