Skip to main content
Glama
meritz-mcp

meritz-mcp

Official

합성 시세 백테스트

meritz_backtest_demo
Read-only

Run a backtest demo using synthetic quotes to simulate trading strategies and generate reports without real market data.

Instructions

합성 시세로 보고서를 시연합니다. 실제 종목·고객 시세가 아닙니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "meritz_backtest_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
fastNo
slowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

C2.8/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=false, so the safety profile is covered structurally. The description contributes one genuinely useful behavioral fact beyond that — the output is based on synthetic quotes and is not real ticker or customer data — which prevents the agent from treating results as market truth, but it says nothing about how the demo report is produced or whether anything persists.

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?

Two short sentences with no redundant wording, and the demonstration purpose is front-loaded ahead of the synthetic-data caveat. It is efficient, though the extreme brevity borders on under-specification given the undocumented parameters.

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 simple two-optional-parameter, read-only demo tool with annotations covering the safety profile and no output schema, the description gives the one essential caveat (synthetic data). It is still missing what the returned report looks like and what the parameters control, which matters because the name 'demo' alone does not tell the agent what to expect back.

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% for two parameters (fast and slow, defaults 5/20, bounds 2–120), so the schema supplies types and ranges but no meaning. The description does not mention fast or slow at all, leaving the agent to guess that these are short and long window lengths; it fails to compensate for the coverage 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 description says the tool 'demonstrates a report with synthetic quotes' (합성 시세로 보고서를 시연합니다), which conveys a demo/sample purpose and implicitly separates it from real backtest siblings via the 'not real quotes' caveat. However, the verb is vague ('demonstrate a report') and it never states that a backtest is being run or what the report actually contains, so the agent must lean on the tool name and title.

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 explicit when-to-use or when-not-to-use guidance, and no sibling tool (e.g. meritz_backtest_run, meritz_backtest_compare) is named as the alternative for real-data runs. The only implicit guidance is the statement that the data is synthetic, leaving the agent to infer that this is for demonstration only.

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