Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

미납 과태료 조회

efine__unpaid_penalty__query
Read-only

REQUIRES prior efine__session__login call with same account_link_id. Read-only. Lists unpaid administrative fines. Set all_period true for everything, or false and give a range - date_basis picks whether the range means the payment due date or the violation date. Paying is 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. 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_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?

Consistent with readOnlyHint=true/destructiveHint=false and goes well beyond them: token cost per call, file retention (15-minute download links, 7-day storage), recovery via xdata__job__result with job_id, and detailed anonymous recovery_receipt semantics. This is rich behavioral context an agent cannot get from annotations alone.

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?

Front-loads the critical prerequisite and read-only nature, which is good. But it then sprawls into generic platform boilerplate (recovery receipts, idempotency key mechanics, anonymous access rules) that dilutes the tool-specific content, and the trailing Korean token-cost line is orphaned without structure.

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 helpfully explains the artifacts[] return shape, download_url lifetime, and file retention, plus recovery paths for expired and anonymous results. That covers the output/return story well, leaving only minor gaps such as result payload fields.

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 every parameter is already documented in the schema. The description reinforces the all_period/date_basis interaction but adds little semantic detail beyond what the schema fields already provide, so the baseline of 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?

States a specific verb and resource: 'Lists unpaid administrative fines,' and adds scope details ('Paying is not offered'). It does not explicitly differentiate from the very similar siblings efine__paid_penalty__query, efine__unpaid_violation__query, or efine__paid_violation__query, which is the main clarity gap.

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 on prerequisites and modes: requires a prior efine__session__login with the same account_link_id, explains the all_period-vs-range choice and how date_basis interprets the range, and states paying is not offered. However, it never names an alternative sibling tool or says when unpaid violation/paid penalty queries should be chosen instead.

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