Skip to main content
Glama
meritz-mcp

meritz-mcp

Official

사용자 전략 코드 확인

meritz_backtest_validate
Read-only

Validates the syntax and entry point of an on_bar(ctx) Python strategy without executing code or providing security authentication, helping catch structural errors before running a backtest.

Instructions

on_bar(ctx) Python 전략의 문법·진입점을 검사합니다. 코드를 실행하지 않으며 보안 인증이 아닙니다.

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": {
      "code": "<code>"
    },
    "name": "meritz_backtest_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, but the description still adds meaningful behavior for arbitrary user code input: validation is static and the code is NOT executed, and it is not a security authentication step. Those two negative guarantees are exactly the facts an agent needs before sending untrusted strategy code. It does not say whether validation is strict or best-effort, or what happens on failure, so it is not a 5.

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, front-loaded with the purpose and immediately followed by the two constraints that most affect safe invocation. There is no filler and no repetition of the title or schema.

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?

For a one-parameter validation tool with an output schema (so return values need not be described) and annotations covering the safety profile, the description is nearly sufficient: purpose, entry-point expectation, no-execution, and non-auth are all covered. What is missing is any statement about strictness of validation or how failures surface, which leaves a small gap for an agent deciding whether to trust a pass result.

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% for the single required 'code' parameter, so the description carries the burden. It does add real meaning by specifying that the code is an on_bar(ctx) Python strategy, which tells the agent the required entry-point signature, but it says nothing about encoding, whether partial snippets are accepted, or the 65536-character cap.

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 (검사합니다 / validate) on a specific resource: the syntax and entry point of an on_bar(ctx) Python strategy. That is far more precise than the title '사용자 전략 코드 확인', and the 'does not execute code' clause implicitly separates it from the run/execute siblings. It stops short of explicitly naming the sibling to use instead, which keeps it from a 5.

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?

Usage is only implied: an agent can infer this is a pre-flight check before meritz_backtest_run, but no condition, ordering, or alternative is stated. The phrase '보안 인증이 아닙니다' functions as a small when-not hint (don't use it as a security/authorization gate), but the description never names the tool that would be appropriate for execution or verification.

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