Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

고용보험 보험료 요약

payroll_pack__employment_insurance_summary_v1__generate
Read-only

Composite employment-insurance summary v1: runs COMWEL premium billing notice search then employment detail as internal steps, and returns computed employment_insurance_won: the unemployment-benefit portion of the institution notice billed to the workplace, including BOTH employee and employer portions. It is NOT the employee payroll-deduction amount; compute the employee share separately. Requires prior comwel session login. No account_link_id is needed here: each step finds its own institution link. If computed is null the result could not be assembled: read computed_error for the reason and do not present the result as complete. Two shapes carry that case: this envelope with partial set to true (we fetched everything - the legs hold it - but could not calculate), or an error whose data carries the same envelope. partial is true whenever the result is incomplete, whether a leg failed or the calculation did. 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 pack_run_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. 호출마다 토큰 1소진

Input Schema

NameRequiredDescriptionDefault
billing_yearYesBilling year in YYYY format
billing_monthYesBilling month 1-12 (string or integer)
output_formatsNoOptional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
idempotency_keyNoOptional outer idempotency key; leg keys are derived deterministically from this value.
business_management_noNoOptional COMWEL business management number; defaults to the logged-in workplace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / output_formats
      Added value: +{
+  "description": "Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.",
+  "items": {
+    "enum": [
+      "xlsx"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

Far beyond the readOnlyHint/destructiveHint annotations, it discloses failure semantics (computed null → read computed_error; two envelope shapes with partial=true), artifact lifetime (download_url 15 minutes, file kept 7 days), recovery paths (xdata__job__result with pack_run_id), and per-call cost (1 token). It also warns that anonymous results are unrecoverable without the private recovery_receipt, which an agent cannot learn from any structured field.

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 purpose and the computed-vs-error rule are correctly front-loaded, but the tail sprawls into recovery_receipt custody rules ("Do not publish it", "Losing it cannot be repaired by signing up") that read as policy prose rather than call guidance. Several sentences are multi-clause run-ons, and the Korean token note dangles at the very end.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the entire contract and does: it defines the returned field (employment_insurance_won, employee + employer portions), the incomplete-result signal (partial, computed_error), the artifact manifest, and the auth/recovery preconditions. An agent has what it needs to call it and to interpret both success and failure.

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; the description earns above baseline by explaining that files appear only when output_formats requests xlsx and that they surface in artifacts[], and by pre-empting the account_link_id question the schema never raises. billing_year/billing_month semantics are left entirely to the schema, so not a 5.

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?

"Composite employment-insurance summary v1" plus "runs COMWEL premium billing notice search then employment detail" names the verb, the resource and the steps, and the explicit "It is NOT the employee payroll-deduction amount" sharpens the boundary. It never names the closest sibling (payroll_pack__premium_summary_v1__generate), so an agent must infer the split rather than read it.

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 states a prerequisite ("Requires prior comwel session login") and a null-account rule ("No account_link_id is needed here"), which is real usage context. But it gives no when-to-use/when-not against the sibling premium_summary_v1 or insurance_deduction_material_v1 tools, so selection between near-identical packs is left to guesswork.

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