XBOSS

급여대장 엑셀 생성

payroll_artifact__register_xlsx

Build a standard payroll register workbook (xlsx) from attribution_ym and employees[] (tax/deduction amounts already computed). Platform key only — no account_link_id. Result: a summary in data (attribution_ym, employee_count) and the workbook in artifacts[] with a signed download_url (not composite merge). Files: a document generated from this result, as Excel (xlsx), 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "attribution_ym": "<attribution_ym>",
      "employees": "<employees>"
    },
    "name": "payroll_artifact__register_xlsx"
  }
}

Input Schema

Name	Required	Description
`employees`	Yes	Employee rows with name, birth_date, dependent counts, pay/allowance/deduction/tax/net amounts in won.
`company_name`	No	Alias for workplace_name
`attribution_ym`	Yes	Payroll attribution month as YYYYMM (e.g. 202603).
`workplace_name`	No
`workplace_address`	No
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.
`business_registration_no`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, and the description is consistent, stating outright that 'this call is not purely read-only' and that each call creates an XBOSS job and consumes one token. It also discloses artifact retention (7 days), download_url lifetime (15 minutes), and the anonymous recovery_receipt semantics, which go well beyond the annotations. The receipt and idempotency passages read as generic platform boilerplate and are not specific to producing a payroll register.

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 opening sentence is well front-loaded, but the body sprawls across receipt recovery, publishing prohibitions, sign-up consequences, and idempotency rules that largely duplicate the schema's own request_idempotency_key note. For a single workbook-generation tool, several sentences (e.g. 'Do not publish it. Losing it cannot be repaired by signing up.') do not earn their place in the primary description.

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 correctly carries the return contract: a summary in data (attribution_ym, employee_count) and the workbook in artifacts[] with a signed download_url. It also explains the expiry/recovery path, which an agent needs after the fact. Gaps are minor — no mention of validation-failure behavior or how the optional workplace fields affect the generated document.

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 57%, so the schema already documents the most important fields (attribution_ym format, employees item structure, alias behavior). The description adds two genuinely useful facts: 'Platform key only — no account_link_id' and that the won amounts arrive pre-computed, which tells the agent not to derive deductions. It says nothing about workplace_name/company_name precedence, workplace_address, or business_registration_no, leaving the uncovered half undocumented in both places.

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 first sentence gives a specific verb and resource: 'Build a standard payroll register workbook (xlsx) from attribution_ym and employees[]', and it clarifies that tax/deduction amounts are already computed, so the agent knows this is a rendering step, not a calculation step. It does not explicitly name its closest sibling payroll_artifact__payslip_xlsx, so the register-vs-payslip distinction is left to the tool name rather than stated.

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?

It gives real conditional guidance for downstream steps — 'If a link has expired, call xdata__job__result with the job_id' and when to reuse vs regenerate request_idempotency_key — plus a precondition that amounts must already be computed. What is missing is when to choose this tool over the sibling payslip/pack generators, and whether it can be called standalone or only after a payroll computation step.

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?