toss-invest-mcp

fx_usdkrw

Read-only

Retrieves the current USD/KRW exchange rate as displayed by Toss, refreshed every minute for reference only and not guaranteed to match actual execution rates.

Instructions

원/달러 환율 (토스 표시 환율, 1분 갱신. 실제 체결 환율과 다를 수 있음).

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 25, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already state readOnlyHint, openWorldHint, and destructiveHint=false. The description adds meaningful behavior beyond that: a 1-minute refresh cadence, the Toss data source, and a caveat that the displayed rate may differ from the actual execution rate.

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?

A single front-loaded sentence states the resource, source, refresh interval, and caveat with no wasted text. Every clause adds information an agent would want before calling the tool.

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?

The tool has no parameters, an output schema, and safety annotations, so the description does not need to explain return values. It supplies the key source, freshness, and caveat context; only explicit sibling routing is missing.

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?

There are zero parameters, so the schema imposes no semantic burden and the baseline is 4. The description correctly focuses on the returned rate rather than inventing parameter details.

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 names the exact resource (USD/KRW exchange rate) and the data source (Toss displayed rate), so the tool's purpose is immediately clear. It does not explicitly distinguish itself from siblings like quote or market_hours_us, but the resource is specific enough to avoid confusion.

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

Usage Guidelines3/5

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

Usage is implied by the resource name, but the description offers no explicit guidance on when to use this tool versus related siblings such as quote or kr_market. The caveat about differing from actual execution rates is useful context but not usage direction.

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

Deploy Server