Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

증명서 신청 목록 조회

hometax__certificate__list
Read-only

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소진

Input Schema

NameRequiredDescriptionDefault
end_dtNoApplication end date YYYYMMDD or YYYY-MM-DD. Optional; omitting it means today. Send together with strt_dt.
strt_dtNoApplication 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_numNoPage number (default 1)
page_sizeNoPage size (default 10)
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. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds substantial behavior: login prerequisite, empty-result trap when dates are omitted, the institution returning an empty list instead of an error for over-long ranges, idempotency-key lifecycle, and token consumption. This is rich operational context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and prerequisites are front-loaded, and most sentences carry important caveats. It is dense as a single paragraph, and the idempotency-key discussion plus the trailing token note add some verbosity, but the core content earns its place.

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 read-only list with no output schema, the description covers the critical prerequisites, date-range behavior, empty-result pitfall, idempotency, and token cost. Return values are only briefly described as applications with receipt ids, and pagination behavior is not explained, so it is strong but not fully complete.

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 schema already documents all six parameters. The description still adds meaningful semantics for the date parameters (empty-result caveat, monthly split rationale) and carries detailed idempotency-key usage because the schema defers to the description; page_num/page_size are left to the schema, so 4 rather than 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: list certificate applications already filed at Hometax, including receipt ids (cvaId, rcatNo). The phrase 'already filed' distinguishes it from sibling apply tools, and 'list' distinguishes it from download/list_templates.

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?

It gives clear prerequisites and operating context: prior session login with the same account_link_id, date pairing rules, the 3-day default window, and the one-month maximum requiring monthly splits. It does not explicitly name alternative sibling tools or state when not to use this tool, which keeps it below a 5.

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