Skip to main content
Glama
toss-invest-mcp

toss-invest-mcp

by jihwan0102

stock_info

Read-only

Retrieve basic stock details—including name, market, currency, listing status, and leverage factor—for one or more symbols to identify and validate securities.

Instructions

종목 기본 정보: 이름, 시장, 통화, 상장 상태, 레버리지 배수(leverageFactor) 등.

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": {
      "symbols": "<symbols>"
    },
    "name": "stock_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety and external-call profile. The description adds nothing behavioral beyond listing output fields — no auth needs, rate limits, or symbol resolution behavior — and the field list is largely redundant with the output schema.

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?

A single tight sentence with the resource front-loaded and no filler. Its brevity is a virtue, though it borders on under-specification rather than waste.

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?

With an output schema present and annotations covering safety, the return values and read-only nature need no restating. The remaining gap — undefined `symbols` format — is the one thing an agent actually needs to call correctly, and it is missing.

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 0% and the single `symbols` string parameter is undocumented in both schema and description. The description does not state format (comma-separated? array-in-string? exchange prefix?) or whether multiple symbols are accepted, leaving the most important calling detail ambiguous.

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 resource (종목 기본 정보) and enumerates the exact fields returned: name, market, currency, listing status, leverage factor. This clearly separates it from price/orderbook siblings like quote, orderbook, and candles, though it never explicitly contrasts itself with them.

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 when-to-use or when-not guidance, and no mention of alternatives such as quote for pricing. Usage must be inferred from the field list alone.

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