XBOSS

신한은행 계좌 목록 조회

shinhan_easy__accounts__list

REQUIRES prior shinhan_easy__auth__id_password_session__login call with same account_link_id. List Shinhan easy-inquiry accounts for a registered account link. 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": "shinhan_easy__accounts__list"
  }
}

Input Schema

Name	Required	Description
`include_raw`	No	Include raw provider response fields
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 서비스에 계정을 여러 개 연동했을 때만 직접 입력해 주세요.
`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.9/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 is consistent with that, adding real context the annotations do not carry: each call consumes one token, it creates an XBOSS task and stores the result, and it is explicitly not purely read-only. Token cost and side-effect persistence are valuable disclosures; the wording is partly boilerplate and split across Korean and English, which slightly blunts the message.

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 critical prerequisite is correctly front-loaded, but the body is long and mixes English and Korean mid-paragraph, and the trailing sentences about XBOSS task creation and provider-data changes read as template boilerplate rather than tool-specific guidance. Information is accurate but not tightly organized.

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 three-optional-parameter list tool, the definition covers the login prerequisite, idempotency lifecycle, token cost and side effects, which are the main things an agent needs to call it correctly. The shape of returned account records is not described, but with no output schema that is a modest gap.

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, but the description goes further on request_idempotency_key: generate and save before the first request, reuse only for lost-response recovery with identical arguments, new key for a new execution, and the key is unavailable to anonymous test calls. It also reinforces that account_link_id must match the login session's link.

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 second sentence names the specific verb and resource: "List Shinhan easy-inquiry accounts for a registered account link." It is distinguishable from the transaction_history search siblings by scope, though it never explicitly names an alternative tool, so a 4 rather than a 5.

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

Usage Guidelines4/5

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

The prerequisite is stated up front and unambiguously: a prior shinhan_easy__auth__id_password_session__login with the same account_link_id is required. It also gives clear rules for when to reuse vs regenerate the idempotency key. It lacks explicit when-not-to-use guidance or named alternatives.

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?