Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

4대보험 FAQ 목록 조회

fourinsure__b1__resources__faqs__list
Read-only

No credential or login required. List FAQs for 4대보험. 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
srch_optNo검색 옵션 srchOpt
srch_txtNo검색어 srchTxt. 별칭 query
srch_sortNo정렬 srchSort
srch_clsf_cdNo분류 코드 srchClsfCd
srch_type_cdNo유형 코드 srchTypeCd
current_page_noNo페이지 번호 currentPageNo. 기본 1
srch_cvlcpt_typeNo민원 유형 검색 srchCvlcptType
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. Changed7 schema fields changed
    • addedInput schema / properties / current_page_no
      Added value: +{
+  "description": "페이지 번호 currentPageNo. 기본 1",
+  "type": "integer"
+}
    • addedInput schema / properties / srch_clsf_cd
      Added value: +{
+  "description": "분류 코드 srchClsfCd",
+  "type": "string"
+}
    • addedInput schema / properties / srch_cvlcpt_type
      Added value: +{
+  "description": "민원 유형 검색 srchCvlcptType",
+  "type": "string"
+}
    • addedInput schema / properties / srch_opt
      Added value: +{
+  "description": "검색 옵션 srchOpt",
+  "type": "string"
+}
    • addedInput schema / properties / srch_sort
      Added value: +{
+  "description": "정렬 srchSort",
+  "type": "string"
+}
    • addedInput schema / properties / srch_txt
      Added value: +{
+  "description": "검색어 srchTxt. 별칭 query",
+  "type": "string"
+}
    • addedInput schema / properties / srch_type_cd
      Added value: +{
+  "description": "유형 코드 srchTypeCd",
+  "type": "string"
+}
  3. Added

TDQS

C2.9/5.0
Behavior3/5

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

"No credential or login required" and "호출마다 토큰 1소진" add real context beyond readOnlyHint/destructiveHint: anonymous access and a per-call cost. However, most of the paragraph concerns request_idempotency_key, which is described as unavailable to anonymous calls and therefore largely inapplicable to this read-only list, muddying rather than clarifying behavior.

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 core statement is one short sentence, but it is followed by six sentences of idempotency-key protocol that do not apply to an anonymous read-only list call and obscure the actual purpose. Front-loading is fine, but the bulk of the text does not earn its place.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter search endpoint with no output schema, the description explains none of the return shape, pagination, or what the search fields filter. Instead it spends its capacity on key handling that the description itself says anonymous callers cannot use, leaving the practical calling contract underspecified.

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 eight search parameters are already documented in the schema; the description adds nothing about srch_opt, srch_txt, srch_clsf_cd, current_page_no, or pagination behavior. Baseline 3 applies when the schema carries the full parameter burden.

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?

States a specific verb and resource ("List FAQs for 4대보험") and covers the anonymous-read nature, so the agent knows what it retrieves. It does not distinguish itself from the closely named siblings faqs__detail and faqs__list_init, which an agent could easily confuse with a plain list.

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

Usage Guidelines2/5

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

The only routing signal is "No credential or login required"; there is no guidance on when to pick this over faqs__detail (fetch a specific FAQ) or faqs__list_init (the init handshake that typically precedes this list). The agent must infer the sequence from sibling names alone.

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