Skip to main content
Glama

기관 공지 상세 조회

fourinsure__b1__resources__notices__institutions__detail

자격증명이나 로그인 없이 바로 호출할 수 있습니다. 기관 공지 한 건의 상세를 조회합니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 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": {
      "pst_sn": "<pst_sn>"
    },
    "name": "fourinsure__b1__resources__notices__institutions__detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
pst_snYes게시 일련번호. 기관 공지 목록 조회 결과에서 받습니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request_idempotency_key / description
      Previous value: -"Optional same-request recovery key for authenticated calls; see the tool description."New value: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  2. Changed1 schema field changed
    • changedInput schema / properties / pst_sn / description
      Previous value: -"Post serial number (게시 일련번호). Obtain from institutions.list."New value: +"게시 일련번호. 기관 공지 목록 조회 결과에서 받습니다."
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, and the description earns that by disclosing the non-obvious side effects: each call consumes a token, creates an XBOSS task and stores the result, so the call is explicitly "순수 읽기 전용이 아닙니다" despite being a retrieval. It also spells out the idempotency replay contract (same key + same args only to recover an unanswered request, new key for a new execution) and warns that a similarly named institution-level idempotency_key field must be left alone — real value beyond the annotations.

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?

Useful information is front-loaded (no credentials, then the retrieval purpose), but the idempotency paragraph is repetitive — "이 값 없이 다시 부르면 새 요청이 됩니다" restates the preceding sentence — and the trailing sentence about institution data changes is generic boilerplate that does not apply to this read-shaped call.

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 single-record detail tool with a fully documented 3-parameter schema and no output schema, the description covers auth, cost, side effects, and idempotency recovery well. The only real gap is that it never indicates what the detail response contains or whether attachments require a separate sibling call.

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 coverage is 100%, so all three parameters are already documented, including account_link_id's fallback-to-API-key behavior and per-institution ID variance. The description only deepens request_idempotency_key usage (which the schema explicitly defers to it) and distinguishes it from the unrelated institution idempotency_key field, so it adds modest value over an already complete 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?

"기관 공지 한 건의 상세를 조회합니다" gives a specific verb (조회) and a precisely scoped resource (one institution notice), which separates it from the sibling list/attachments tools by name and cardinality. It stops short of explicitly contrasting itself with those siblings, but the resource scope is unambiguous.

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 is strong on preconditions — callable without credentials or login, and the optional idempotency field is unusable in anonymous 'taster' mode — but it never states when to pick this tool over the list or attachments siblings, nor that pst_sn must first be obtained from the list call (that hint lives only in the schema).

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