tossinvest-mcp

List brokerage accounts

tossinvest_list_accounts

Read-onlyIdempotent

List reachable Toss Securities brokerage accounts to identify the account sequence needed for account-scoped actions. Returns account numbers and types, helping you choose the right account before trading.

Instructions

List the Toss Securities accounts reachable with the configured credentials.

Call this first when you do not know which account to act on. The 'accountSeq' in the response is what every account-scoped tool takes as 'account_seq'.

Args:

response_format ('markdown' | 'json'): default 'markdown'.

Returns { count, accounts: [{ accountNo, accountSeq, accountType }] }. Only BROKERAGE (종합매매) accounts are exposed today; child accounts are not usable. An empty list means the credentials have no brokerage account.

When exactly one account exists, other tools resolve it automatically, so you rarely need to pass account_seq by hand.

Rate limit: the ACCOUNT group allows only 1 request per second.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`response_format`	No	Output format: 'markdown' for a compact human-readable summary, 'json' for the complete raw payload.	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`accounts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare this as read-only, idempotent, and non-destructive. The description adds meaningful behavioral context beyond annotations: only BROKERAGE (종합매매) accounts are exposed, child accounts are not usable, an empty list means no brokerage account, and the ACCOUNT group rate limit is 1 request/second. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact yet information-dense. It front-loads the core purpose and usage guidance, then uses labeled sections for args, returns, caveats, and rate limit. Every sentence earns its place; the structure helps an agent scan quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a discovery tool, the description covers all relevant guidance: output format, return shape, account scope limitations, empty-list semantics, automatic resolution of a single account, and rate limiting. An agent can correctly decide when and how to call this tool without needing additional context.

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?

The only parameter, response_format, is fully documented in the schema with enum, default, and description. The description's 'Args' line restates the default but adds no meaning beyond the schema. Schema coverage is 100%, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'List the Toss Securities accounts reachable with the configured credentials.' It also explains the accountSeq field's role in every account-scoped tool, distinguishing this discovery tool from the many sibling tools that consume account_seq. No ambiguity or tautology.

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

Usage Guidelines5/5

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

Explicit guidance is given: 'Call this first when you do not know which account to act on.' It further tells the agent when it can skip manually passing account_seq ('When exactly one account exists, other tools resolve it automatically'), which refines the decision of whether to call this tool at all.

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

Deploy Server