toss-invest-mcp

holdings

Read-only

Retrieve current stock positions and valuation profit/loss, optionally filtered by symbol to inspect a single position.

Instructions

보유 주식과 평가손익. symbol 을 주면 그 종목만.

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": "holdings"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 25, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety behavior is covered externally. The description adds that results are holdings with valuation P/L and that symbol filters to one item, but it does not disclose empty-state behavior, account scope, or other operational details.

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 two short, front-loaded sentences with no filler. The primary purpose comes first and the optional parameter behavior follows immediately.

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 simple read-only holdings tool with annotations and an output schema, the description provides the essential purpose and filtering behavior. The main remaining gap is symbol format and scope, but the structured fields cover much of the surrounding 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?

Schema coverage is 0%, so the description must carry the parameter meaning. It does explain that providing symbol restricts results to that single stock, but it does not define accepted symbol formats or explicitly state that omitting symbol returns all holdings.

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 identifies the resource as held stocks and valuation profit/loss, and notes that an optional symbol narrows results to one holding. It is specific enough to distinguish the tool from sibling trading/order tools, though it does not explicitly name alternatives.

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?

The description gives only a filtering rule for the optional symbol parameter. It does not explain when to use this tool versus related tools such as orders or stock_info, nor does it state any exclusions or prerequisites.

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

Deploy Server