toss-invest-mcp

place_order

Destructive

Executes a previously previewed stock order after explicit user confirmation, passing any required six-digit verification code; each preview ID can be submitted only once.

Instructions

preview_order 로 만든 주문을 실행한다. 사용자가 미리보기를 보고 명시적으로 실행하라고 했을 때만 호출. 확인코드(폰 전송) 설정이면 사용자가 직접 입력한 6자리 코드를 confirm_code 로 넘긴다. 같은 preview_id 는 한 번만 실행된다.

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": {
      "preview_id": "<preview_id>"
    },
    "name": "place_order"
  }
}

Input Schema

Name	Required	Description	Default
`preview_id`	Yes
`confirm_code`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 25, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare destructive, open-world, non-idempotent, so the safety profile is covered; the description adds genuinely useful behavior a schema cannot express: a given preview_id executes only once, and confirmation codes are user-supplied rather than generated. There is mild tension with idempotentHint=false, but the single-execution rule reads as a dedupe guard rather than a claim that repeats are harmless.

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?

Three sentences, no filler, with the precondition and the confirm-code rule front-loaded ahead of the edge-case detail. Every sentence carries information an agent needs.

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?

A destructive, open-world trading tool whose annotations and output schema are already rich; the description adds the missing pieces — preconditions, the confirm-code branch, and the one-shot execution guard — so an agent can call it safely without guessing.

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 0%, so the description must carry the burden, and it does: it explains that confirm_code is the user-supplied 6-digit phone code and is only relevant when confirmation is configured, and that preview_id is the handle from preview_order. It is not exhaustively precise about preview_id's format, but the meaning of both params is clear.

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?

States a specific verb (execute/실행) and resource (an order produced by preview_order), and explicitly ties it to the sibling preview_order so the preview-vs-execute split 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 Guidelines5/5

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

Explicitly restricts invocation to the case where the user has seen the preview and asked to execute, and adds a second condition for the confirm-code flow. An agent knows both when to call this and when not to.

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

Deploy Server