Skip to main content
Glama
meritz-mcp

meritz-mcp

Official

메리츠 시세 백테스트

meritz_backtest_run
Read-only

Backtest an SMA crossover strategy on Meritz domestic daily bars using a registered account, with configurable fast/slow windows over up to one year. Research only; no real orders.

Instructions

등록된 고객 계좌의 키로 메리츠 국내 일봉을 조회해 SMA 전략을 검증합니다.

계좌가 여러 개면 meritz_info로 이름을 확인하여 account를 지정하세요. API 키를 인자로 넣지 마세요. TJ/Y 기준, 최대 1년. 실주문 없음. 세금·유동성·기업행사 미반영 연구용 결과입니다.

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": {
      "symbol": "<symbol>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "meritz_backtest_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
fastNo
slowNo
symbolYes
accountNo
endDateYes
startDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: no real orders are placed, results are research-grade with taxes, liquidity, and corporate actions excluded, and one year is the maximum lookback. Against that, the "TJ/Y 기준" phrase is unexplained jargon, and with no output schema the description never says what the backtest result looks like.

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?

Front-loaded with purpose, then guidance, then caveats, in a tight multi-line block with no filler. The only slack is the cryptic "TJ/Y 기준" fragment, which adds confusion rather than information.

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?

For a six-parameter tool with zero schema descriptions and no output schema, the definition should cover strategy parameters and returns. It covers authentication, account selection, the date ceiling, and result caveats, but leaves the SMA window parameters and the shape of the output unexplained, which is a meaningful gap for a backtest tool.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the parameter burden. It explains `account` well (resolve via meritz_info, do not pass keys) and implies the one-year cap on `startDate`/`endDate`, but `fast` and `slow` are only obliquely implied by "SMA 전략" and `symbol` is never mentioned at all, leaving half the parameters uninterpreted.

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: fetches Meritz domestic daily bars via a registered account key and validates an SMA strategy. That is discernible without opening the schema. However, it never distinguishes itself from the many similar siblings (meritz_backtest_validate, meritz_backtest_demo, meritz_backtest_compare, meritz_backtest_code), so an agent cannot tell which backtest variant to pick from the description alone.

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?

Gives concrete operational guidance: if multiple accounts exist, look up the name with meritz_info and then set `account`, and never pass an API key as an argument. It also bounds the run at a maximum of one year. What is missing is any statement of when to choose this tool over the sibling backtest tools.

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