Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

신한은행 계좌 목록 조회

shinhan_easy__accounts__list
Read-only

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소진

Input Schema

NameRequiredDescriptionDefault
include_rawNoInclude raw provider response fields
account_link_idNoAccount link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple connections for the same provider.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / request_idempotency_key
      Added value: +{
+  "description": "Optional same-request recovery key for authenticated calls; see the tool description.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[\\x20-\\x7E]+$",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / account_link_id / description
      Previous value: -"Account link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure)."New value: +"Account link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple connections for the same provider."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint, and the description adds genuinely new context: authentication ordering requirement, one-token-per-call cost (개인사업자 호출마다 토큰 1소진), and idempotency recovery semantics. These are traits beyond the structured data.

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?

Purpose and prerequisite are front-loaded, but the idempotency block is disproportionately long for an optional 0-required parameter and pushes overall length toward bloat. Each sentence is meaningful but the balance is off.

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?

Covers prerequisites, cost, and idempotency thoroughly for a read-only list tool with no output schema. Only minor gap is that it doesn't indicate what the returned account list contains, though 'list accounts' implies it.

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 baseline is 3; the description exceeds this by explaining the lifecycle of request_idempotency_key (recover-a-lost-response vs new-execution, not available to anonymous calls, distinct from provider idempotency_key) which the schema does not convey. account_link_id linkage is also noted.

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?

States a specific verb and resource: 'List Shinhan easy-inquiry accounts for a registered account link.' An agent can identify the operation. It does not explicitly distinguish from the sibling shinhan_easy__accounts__transaction_history__search or linked_accounts__list, so it falls short of 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?

Explicitly names the required precondition (prior auth__id_password_session__login with same account_link_id) and gives detailed when-to-reuse vs when-to-new guidance for the idempotency key. Lacks explicit routing against sibling tools, so not a 5.

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

All XBOSS toolsInspect
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