XBOSS

서식 목록 조회

fourinsure__b1__resources__forms__list

No credential or login required. List available forms. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fourinsure__b1__resources__forms__list"
  }
}

Input Schema

Name	Required	Description
`srch_txt`	No	검색어 srchTxt. 별칭 query
`srch_job_cd`	No	업무 코드 srchJobCd
`srch_insu_cd`	No	4대보험 코드 srchInsuCd
`srch_pubap_cd`	No	공개범위 코드 srchPubapCd
`current_page_no`	No	페이지 번호 currentPageNo. 기본 1
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds material context beyond them: one token per call, XBOSS task creation/result storage, and that the call is not purely read-only. The idempotency-key guidance further discloses recovery behavior, though some generic provider-idempotency wording adds noise.

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 core purpose and auth constraint are front-loaded, but the description is longer than needed for a simple list tool and mixes generic idempotency boilerplate with Korean operational notes. Some phrasing ('anonymous taste calls') and the provider-specific idempotency-key aside reduce crispness.

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

Completeness3/5

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

The description covers authentication, idempotency, token cost, and the non-read-only side effect, which is important for a tool with readOnlyHint=false. It does not describe the returned form list, pagination behavior, or result fields, and no output schema fills that gap, so completeness is only moderate.

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 still adds meaning for request_idempotency_key by explaining generation, reuse, and anonymous-call limits. It does not add much for the five search/paging parameters, but the schema already documents those.

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 description states 'List available forms,' giving a specific verb and resource. It does not distinguish this operation from siblings such as forms__list_init, forms__detail, or forms__attachments, so an agent must infer the distinction from names.

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 an authentication prerequisite ('No credential or login required') and explains authenticated idempotency-key usage, which is useful context. However, it never says when to choose this list tool instead of sibling form list/detail/init tools, leaving alternative selection implicit.

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?