Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

기업정보·리스크 브리프 v1

company_info_pack__brief_v1__generate
Read-only

Composite company-info brief v1: runs REDUCE-5 opendata steps (nts.status, nts.validate, g2b.sanction, kiscon.sanction, env.waste_sanction), then builds a computed brief. No account_link_id and no certificate are needed: every step runs on our platform key. Empty sanction matches must not be treated as proven clean. 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 PDF 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. 호출마다 토큰 4소진

Input Schema

NameRequiredDescriptionDefault
p_nmYesRepresentative name for nts.validate
biznoYes10-digit business registration number (outer SSOT)
eDateYeskiscon window end YYYYMMDD (sDate<=eDate)
sDateYeskiscon window start YYYYMMDD
start_dtYesOpening date YYYYMMDD for nts.validate
corp_nameNoOptional corp name fallback for kiscon matching
output_formatsNoOptional. Also return this result as a file (PDF) in artifacts[] of the result. Omit it for data only.
idempotency_keyNoOptional outer idempotency key; leg keys are derived deterministically from this value.

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 (PDF) in artifacts[] of the result. Omit it for data only.",
+  "items": {
+    "enum": [
+      "pdf"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint/destructiveHint), and the description adds a great deal beyond them: per-call token cost (4), the failure semantics of a null computed with computed_error, the meaning of partial and the two envelope shapes, 15-minute download links with 7-day file retention, and the anonymous recovery_receipt contract (scope, non-repairability, non-transferability). This is materially more than the annotations convey and does not contradict them.

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?

It is correctly front-loaded with the pipeline, but the receipt/link passage is a dense run-on that repeats itself ('partial is true whenever the result is incomplete' restates the preceding sentence) and mixes languages ('호출마다 토큰 4소진'). The content is largely justified, but the packaging makes it harder to parse than it needs to be.

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 carries the return-value burden and does describe the envelope (computed, computed_error, partial, artifacts[] with download_url, pack_run_id). It still does not say what fields the brief actually contains, so an agent knows the shape but not the payload.

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 description coverage is 100%, so the schema already explains every one of the 8 parameters (bizno, p_nm, start_dt, sDate/eDate, output_formats, idempotency_key). The description adds only indirect context (which upstream legs the parameters feed, and that output_formats PDF lives in artifacts[]); the baseline of 3 is appropriate.

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?

States a specific verb+resource ('Composite company-info brief v1') and enumerates exactly what it composes: the REDUCE-5 opendata legs (nts.status, nts.validate, g2b.sanction, kiscon.sanction, env.waste_sanction) plus a computed brief. That lets an agent distinguish it from the individual sibling opendata leg tools and from xdata__job__result without opening any schema.

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?

Explicitly removes the usual prerequisites ('No account_link_id and no certificate are needed: every step runs on our platform key') and routes the agent to xdata__job__result when a download link expires, naming the pack_run_id to pass. It stops short of stating when an agent should call the individual opendata legs instead of the pack, and gives no exclusion conditions.

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