Skip to main content
Glama

4대보험 FAQ 목록 조회

fourinsure__b1__resources__faqs__list

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소진 요청 처리 시 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__faqs__list"
  }
}

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. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations, the description discloses token consumption, creation of an XBOSS task, storage of processing results, and clarifies that the call is not purely read-only. These details materially improve behavioral understanding, though the idempotency language is somewhat repetitive and confusing in places.

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 is front-loaded, but the description is lengthy and includes repetitive idempotency instructions plus a separate Korean behavioral paragraph. Most content is relevant, but several sentences could be tightened without losing invocation-critical information.

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?

For a list tool with eight optional parameters, no output schema, and annotations that already declare safety hints, the description covers the key operational context: anonymous access, idempotency handling, token cost, and side effects. It still omits return-value shape and sibling-tool routing, but it is sufficient to invoke the tool correctly.

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 all eight parameters are already documented. The description adds meaningful semantics specifically for request_idempotency_key, including when to generate it, how to reuse it after a lost response, and when a new key is required, though it adds little beyond the schema for the search parameters.

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 clearly states the specific action and resource: 'List FAQs for 4대보험.' This is enough to distinguish it as a FAQ listing operation, but it does not distinguish it from close siblings such as fourinsure__b1__resources__faqs__detail or faqs__list_init.

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?

It states that no credential or login is required, which gives useful access context, but it does not explain when to use this tool versus faqs__detail, faqs__list_init, or the other resource list tools. There are no explicit exclusions or alternative-routing instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources