XBOSS

서식 첨부파일 조회

fourinsure__b1__resources__forms__attachments

No credential or login required. Get form attachments. 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": {
      "bbs_id": "<bbs_id>",
      "pst_sn": "<pst_sn>",
      "atfl_id": "<atfl_id>"
    },
    "name": "fourinsure__b1__resources__forms__attachments"
  }
}

Input Schema

Name	Required	Description
`bbs_id`	Yes	Board ID (게시판 ID). Obtain from forms.list.
`pst_sn`	Yes	Post serial number (게시 일련번호). Obtain from forms.list.
`atfl_id`	Yes	Attachment file ID (첨부파일 ID). Obtain from forms.list.
`current_page_no`	No	List page the target row was found on. Optional; defaults to 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?

Beyond the annotations, it discloses real operational behavior: each call consumes one token (호출마다 토큰 1소진), an XBOSS task is created and its result stored, and explicitly that the call is not purely read-only despite being a lookup. This corroborates readOnlyHint=false and explains why, rather than contradicting it. It stops short of describing the response or any rate limits beyond the token cost.

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 is one short sentence, but it is followed by a long boilerplate idempotency paragraph and a vague closing line (기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다) that does not add actionable information. The English/Korean mixing makes the block harder to scan than necessary.

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?

Auth, cost, side effects, and idempotency are covered, and there is no output schema to explain. What is missing is the key question for an attachments tool: whether it returns attachment metadata, a download link, or file content, and how multiple attachments are ordered or paginated. An agent cannot tell what it will receive.

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 would be 3; the description earns above that by giving the request_idempotency_key real semantics (generate before the first request, reuse only to recover a lost response, new key for a new execution) where the schema only says "see the tool description." The remaining parameters are left entirely to the schema.

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 sentence "Get form attachments" states a specific verb and resource, matching the Korean title 서식 첨부파일 조회. However, it does not distinguish this from sibling tools such as fourinsure__b1__resources__files__download or fourinsure__b1__resources__notices__institutions__attachments, so an agent must infer the boundary from the name alone.

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?

The description does state a prerequisite ("No credential or login required") and gives detailed guidance on when to reuse vs regenerate the idempotency key. It says nothing, however, about when to call this instead of files__download or the notices attachments tool, nor when not to call it.

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?