Skip to main content
Glama
meritz-mcp

meritz-mcp

Official

백테스트 조건 비교

meritz_backtest_compare
Read-only

Compare moving-average period settings against an existing backtest run using identical price and cost data, without re-fetching market quotes.

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": {
      "runId": "<runId>"
    },
    "name": "meritz_backtest_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
fastNo
slowNo
runIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description's valuable addition is that no market-data re-fetch occurs, which signals speed and reproducibility. It does not say whether the comparison result is persisted, what it contains, or any limits on how many comparisons can run at once.

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 the core action first and the no-refetch guarantee as a trailing qualifier. Every clause earns its place and there is no filler.

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 three-parameter tool with no output schema and zero schema coverage, the description leaves gaps: it never describes the return value beyond 'compare', and gives no parameter constraints. What it does cover, the data-reuse behavior, is the most important thing an agent needs, which keeps it at minimum viable rather than inadequate.

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 parameter meaning and it only partially does: 'moving-average periods' maps to fast and slow, and 'existing run' implies the runId. Nothing explains fast-vs-slow semantics, the 2-120 bounds, the defaults, or the 24-character hex format of runId, so an agent still depends on the bare schema.

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: it compares results by varying the moving-average periods against an existing run. It also implicitly distinguishes itself from a fresh backtest by noting the same quotes and costs are reused. It never names a sibling tool explicitly, so the differentiation is inferred rather than stated.

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?

The phrase about reusing the existing run's quotes and costs implies this should be used when you already have a runId and want a parameter sweep without re-fetching market data. However, it never says when to choose this over meritz_backtest_run or what happens if the runId is invalid or expired, leaving usage conditions only implied.

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