Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

미납범칙금 조회

efine__unpaid_violation__query
Read-only

REQUIRES prior efine__session__login call with same account_link_id. Read-only. Lists unpaid criminal fines with the row count and whether another page follows. Paying, per-row detail and picking another corporation 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.
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.9/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 is consistent ('Read-only'), yet it adds a lot beyond them: download_url lifetime of 15 minutes, 7-day file retention, artifact placement in artifacts[], idempotency-key recovery semantics, and a per-call token cost. The anonymous recovery_receipt passage is extensive and somewhat at odds with the stated login requirement, which muddies the behavioral picture slightly.

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 login prerequisite and read-only nature well, but the body is a dense run-on that mixes file retention, anonymous recovery receipts, idempotency-key policy, and token cost in one block. Several sentences are framework boilerplate that a caller of a logged-in query tool must filter out, and the anonymous-receipt discussion sits awkwardly beside the login requirement.

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?

No output schema exists, and the description compensates by describing the return shape (row count, page-follow flag, artifacts with download_url), retention windows, and the recovery path for expired links. Prerequisites and cost are also covered, so an agent has what it needs to call this correctly, even if the anonymous path is confusing.

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 genuinely adds meaning beyond the schema: it explains that output_formats produces a file in artifacts[] (not just data), and it gives operational semantics for request_idempotency_key (generate before first request, reuse only to recover a lost response, never reuse for a new execution). page_size behavior is only restated, not extended.

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 criminal fines' — plus the return shape (row count, whether another page follows) and an explicit scope exclusion ('Paying, per-row detail and picking another corporation are not offered'). It does not however name the near-identical siblings efine__unpaid_penalty__query or efine__paid_violation__query, so an agent must infer the fine-vs-penalty distinction from the name alone.

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 up front ('REQUIRES prior efine__session__login call with same account_link_id') and states what the tool will not do, which is real when-not guidance. It also routes to xdata__job__result for expired artifact links. Missing an explicit 'use X instead' for the sibling paid/penalty query tools.

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