XBOSS

증명서 신청 목록 조회

hometax__certificate__list

REQUIRES prior hometax__session__login call with same account_link_id. List certificate applications already filed at Hometax (민원증명 발급 목록) with their receipt ids (cvaId, rcatNo). Read-only. Without strt_dt/end_dt only the last 3 days are returned, so an empty result does not mean the taxpayer has no certificates — widen the period to look further back. Send both dates or neither. One call covers at most one calendar month (strt_dt no earlier than end_dt minus one month); a longer period is refused, because the institution returns an empty list for it instead of an error — split it into monthly calls. 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": "hometax__certificate__list"
  }
}

Input Schema

Name	Required	Description
`end_dt`	No	Application end date YYYYMMDD or YYYY-MM-DD. Optional; omitting it means today. Send together with strt_dt.
`strt_dt`	No	Application start date YYYYMMDD or YYYY-MM-DD. Optional; omitting it means 3 days ago. Send together with end_dt. No earlier than end_dt minus one month.
`page_num`	No	Page number (default 1)
`page_size`	No	Page size (default 10)
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false, openWorldHint=false and destructiveHint=false; the description goes well beyond them by disclosing token consumption per call, XBOSS task creation with stored results, and the institution's quirk of returning an empty list rather than an error for oversized ranges. The one flaw is internal tension: it asserts 'Read-only.' early and then states the call is not purely read-only, which is confusing even though the later text matches readOnlyHint=false.

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?

The prerequisite is front-loaded and the date rules are logically ordered, but the text is long and mixes English with Korean boilerplate about token consumption and XBOSS task creation whose relevance to an agent's decision is unclear. The self-contradicting 'Read-only.' sentence adds noise that the reader must reconcile.

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?

For a six-parameter, zero-required read-family tool with no output schema, the description supplies auth prerequisites, date-window behavior, the month ceiling and the idempotency contract, so an agent can call it correctly. Pagination is left entirely to the schema, and the return payload beyond receipt ids is not characterized, which are the remaining gaps.

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, and the description largely restates the date semantics (defaults, pairing, one-month cap) that the schema also carries. It does add genuine meaning for request_idempotency_key by defining reuse-versus-new-key behavior and distinguishing it from a provider-specific idempotency_key, but that is the only clear increment.

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 names a specific verb and resource ('List certificate applications already filed at Hometax (민원증명 발급 목록)') and states what is returned (receipt ids cvaId, rcatNo), which is far better than a tautology. It does not explicitly contrast itself with nearby siblings such as hometax__certificate__list_templates or fourinsure__b1__certificate__history__list, so selection between them is still an inference.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit prerequisite (prior hometax__session__login with the same account_link_id), the default window when dates are omitted, the must-send-both-or-neither rule, the one-calendar-month ceiling, and the prescribed workaround of splitting into monthly calls. It also spells out when to reuse versus regenerate request_idempotency_key, which is exactly the kind of conditional guidance an agent needs.

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

All XBOSS tools Inspect

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

Need Help?