Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by clauzewitz

get_exchange_rate

Read-onlyIdempotent

Retrieve the current KRW↔USD reference exchange rate, refreshed every minute, to estimate conversion values; actual order rates may differ.

Instructions

KRW↔USD 환율(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": "get_exchange_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_timeNo조회 시각(ISO 8601). 생략하면 현재
base_currencyNoUSD
quote_currencyNoKRW

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description still adds real value by disclosing the 1-minute refresh cadence (data staleness) and warning that the value may differ from the actual order exchange rate. What it does not disclose is the response shape — the rate's direction, precision, or timestamp.

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?

Two short sentences with zero filler, and the substantive scope and refresh cadence are front-loaded. The caveat about the order rate is the one sentence that genuinely earns its place.

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 zero-required-parameter read tool with annotations covering the safety profile, the description covers purpose, freshness, and the key caveat. The remaining gap is what the call returns (a single rate? a pair of values with a timestamp?), which no output schema exists to cover.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: date_time carries an ISO 8601 note in the schema, but base_currency and quote_currency have only enums and defaults with no meaning attached. The description does nothing to compensate — it never explains base-versus-quote direction, the USD→KRW default, or how date_time affects the result, so an agent must infer the semantics of two of three parameters.

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 (KRW↔USD 환율), which is enough to separate it from every sibling tool (prices, orderbook, candles, holdings, etc.). It loses a point only because the description narrows scope to KRW↔USD while the schema permits any base/quote combination, leaving that mismatch unaddressed.

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 rather than prescribed: the phrases '참고용' (for reference) and '실제 주문 환율과 다를 수 있다' signal this is an indicative lookup, not a source for settlement or order pricing. There is no explicit when-to-use versus when-not-to-use guidance and no named alternative for authoritative rates.

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