Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

최근단속내역 조회

efine__recent_enforcement__query
Read-only

REQUIRES prior efine__session__login call with same account_link_id. Read-only. Lists recent enforcement records the institution holds, with the row count and whether another page follows. Paying and filing an objection 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
page_sizeNoOptional. Rows per page on the first page. Pages after the first exist only at 10.
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

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true/destructiveHint=false, and the description stays consistent while adding real context: artifact download_url valid 15 minutes, files retained 7 days, idempotency key reuse semantics, and '호출마다 토큰 1소진' cost per call. Much of the receipt/anonymous-result prose is generic boilerplate irrelevant to an authenticated read-only listing, which keeps it below 5.

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?

Roughly 250 words for a simple paginated read, with long stretches of copy-pasted boilerplate about anonymous recovery receipts and 'taste calls' that cannot apply to a login-gated listing. The purpose is front-loaded, but several paragraphs do not earn their place in this tool's definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers prerequisite, result shape (row count, has-next-page), file output and retention, and idempotency, which is reasonable given no output schema. It omits the sibling differentiation and the meaning of vehicle_number filtering, and the generic receipt prose adds noise rather than completeness.

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; the description goes beyond it for two parameters by explaining that output_formats xlsx files land in artifacts[] with a 15-minute download_url and by spelling out when to generate, reuse, or rotate request_idempotency_key. page_size/page_index behavior is 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 concrete verb and resource: 'Lists recent enforcement records the institution holds, with the row count and whether another page follows.' It also rules out paying and filing objections, so the scope is bounded. However, it never distinguishes itself from the four closely named siblings (paid_penalty, paid_violation, unpaid_penalty, unpaid_violation), leaving the agent to infer that this is the generic 'recent' list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/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 excludes payment/objection actions. But it never says when to choose this over the paid/unpaid penalty and violation queries, which is the main routing decision an agent faces here.

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