Skip to main content
Glama
toss-invest-mcp

toss-invest-mcp

by jihwan0102

order_detail

Read-only

Fetch order execution details by order ID, including filled quantity, average fill price, and fees.

Instructions

주문 상세 (체결 수량, 평균 체결가, 수수료 등).

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": {
      "order_id": "<order_id>"
    },
    "name": "order_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the annotation layer—no note on what an 'order detail' lookup returns when the order is unknown, no scoping or freshness context—so it contributes little behavioral value.

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

Conciseness4/5

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

The description is a single compact line with the resource named first and the field list second. It is efficient and free of filler, though the brevity borders on under-specification.

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

Completeness3/5

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

An output schema exists, so return-value explanation in the description is not strictly required, and the annotations cover safety. Still, for a one-parameter read tool the description leaves the parameter's meaning and its relationship to sibling order tools unaddressed.

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?

The schema description coverage is 0%, and the description never mentions the required 'order_id' parameter at all. No format, source, or example for the order identifier is provided anywhere, so the description fails to compensate for the schema gap.

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

Purpose3/5

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

The phrase "주문 상세" identifies the resource (an order's details) and the parenthetical lists what the detail contains (executed quantity, average execution price, fees). However, it is a noun phrase with no verb, and it does not distinguish itself from siblings such as 'orders' (list) or 'order_log', so the agent must infer the difference.

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?

There is no statement of when to use this tool, when to prefer 'orders' or 'order_log' instead, or what preconditions apply. The agent gets no routing guidance from the description.

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