Skip to main content
Glama
Sign In
meritz-securities

meritz-mcp

Official
by meritz-securities
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

메리츠 해외 시세(주식·지수·원자재·환율)

meritz_overseas_market
Read-onlyIdempotent

Retrieves overseas stock, index, commodity, and FX quotes through Meritz Open API, including candles, order books, and trade data for market analysis.

Instructions

메리츠 Open API — 해외 시세(주식·지수·원자재·환율) (13건). api_type 으로 호출할 API 를 고르고 params 에 파라미터를 넣습니다. api_type='describe' 로 부르면 파라미터 설명을 돌려줍니다.

ovs_market_candles_days GET 해외주식 시세추이 조회 (일봉) ovs_market_candles_minutes GET 해외주식 시세추이 조회 (분봉) ovs_market_commodities_prices GET 해외 원자재·달러인덱스 현재가 조회 ovs_market_fx_prices GET 환율 시세 조회 ovs_market_index_candles_days GET 해외지수 시세추이 조회 ovs_market_index_candles_minutes GET 해외지수 시세추이 조회(분봉) ovs_market_index_prices GET 해외지수 현재가 조회 ovs_market_orderbook GET 해외주식 호가 조회 ovs_market_prices GET 해외주식 현재가 조회 ovs_market_prices_after GET 해외주식 애프터장 현재가 조회 ovs_market_prices_daytime GET 해외주식 주간거래 현재가 조회 ovs_market_trades_minutes GET 해외주식 체결추이 조회 (분) ovs_market_trades_ticks GET 해외주식 체결추이 (틱)

Input Schema

NameRequiredDescriptionDefault
paramsNo
accountNo
api_typeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.12
    • addedInput schema / properties / account
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
  2. First observedv0.3.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, openWorld=true, so the safety profile is covered. The description adds the self-describing 'describe' mode, which is genuinely useful, but says nothing about response shape, rate limits, or what happens with an invalid api_type. Useful but thin beyond annotations.

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 prose lines establishing the dispatch model are front-loaded, followed by a scannable table of api_type/verb/description. Every line earns its place, and the enumeration format is more compact than prose would be.

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?

This is a dispatcher over 13 endpoints with an output schema present (so return values needn't be described). The description covers the dispatch mechanism, the valid api_type set, and the describe escape hatch for parameter discovery. The missing piece is routing guidance against the overlapping sibling tools.

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 description coverage is 0% and the params object is an opaque anyOf/additionalProperties bag, so the description carries the full burden. It discharges that reasonably by enumerating all 13 valid api_type values with their semantics and pointing to api_type='describe' for per-call parameters. It still doesn't show the shape of keys inside params, so the agent must make a discovery round-trip.

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 a specific resource — Meritz Open API overseas quotes covering equities, indices, commodities, and FX — and enumerates the 13 underlying GET operations, so an agent can see exactly what it retrieves. It does not distinguish itself from the siblings meritz_forex (which overlaps with ovs_market_fx_prices) or meritz_market, leaving ambiguity about which tool to pick at the top level.

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

Usage Guidelines4/5

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

It explains the dispatch contract ('api_type 으로 호출할 API 를 고르고 params 에 파라미터를 넣습니다') and, crucially, offers a discovery path: api_type='describe' returns parameter descriptions. What's missing is when to use this tool versus the six sibling tools, particularly the overlapping meritz_forex/meritz_market.

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

Deploy Server

Other Tools