Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

미납범칙금 조회

efine__unpaid_violation__query

REQUIRES prior efine__session__login call with same account_link_id. 조회만 합니다. 미납 범칙금 목록을 건수, 다음 쪽이 있는지와 함께 돌려줍니다. 납부, 건별 상세, 다른 법인 선택은 제공하지 않습니다. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "efine__unpaid_violation__query"
  }
}

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_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The description earns credit beyond the annotations by explaining why readOnlyHint=false: each call consumes one token ("호출마다 토큰 1소진") and creates an XBOSS job whose result is persisted, even though the agency source is only read ("기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다"). It also discloses artifact retention (15-minute download URL, 7-day file retention) and idempotency semantics. Some of that text is generic cross-tool boilerplate (anonymous recovery_receipt, taste calls) that does not apply to an authenticated EFINE query and dilutes the signal.

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?

The prerequisite is correctly front-loaded, but the body then drifts into a long mixed Korean/English block about anonymous results, recovery receipts, and generic idempotency policy that is largely irrelevant to this authenticated query. Redundant restatement ("조회만 합니다" followed by the caveat that it is not purely read-only) forces the reader to reconcile two statements that need not both be present.

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 carry the return shape: a list, a count, a next-page flag, and artifacts[] entries with links. Login prerequisite, token cost, persistence, and retention are all covered, so an agent can call it and interpret the result without guessing.

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% and the schema already documents page_size, page_index, output_formats, and account_link_id, including the non-obvious rule that later pages exist only at 10. The description adds real meaning only for request_idempotency_key (generate and save before the first request, reuse only to recover a lost response, new key for a new execution), then defers to the description for the rest.

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 unpaid fines together with the count and whether a next page exists ("미납 범칙금 목록을 건수, 다음 쪽이 있는지와 함께 돌려줍니다"). It also scopes the tool negatively by saying payment, per-item detail, and other-corporation selection are not offered. It never names the closest siblings (paid_violation, unpaid_penalty), so the fine-vs-penalty distinction is left to inference.

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?

"REQUIRES prior efine__session__login call with same account_link_id" gives a hard prerequisite, and the exclusion sentence tells the agent what it should not come here for. There is no explicit "use X instead" routing to a sibling, but the when-to-use context is clear enough to act on.

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