Skip to main content
Glama
meritz-mcp

meritz-mcp

Official

가상 체결 근거

meritz_backtest_trade
Read-only

Retrieves the signal date, price, quantity, cost, and recorded trade rationale for a selected virtual execution using a run ID and trade ID.

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>",
      "tradeId": "<tradeId>"
    },
    "name": "meritz_backtest_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYes
tradeIdYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

B3/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 openWorldHint=false, so the safety profile is covered. The description adds that a historical rationale/evidence record is returned, which is useful, but it discloses nothing about pagination, missing-record behavior, or errors when runId/tradeId do not match.

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?

A single sentence with no filler, and the retrieved field list is front-loaded. Nothing extraneous, though the terseness contributes to the parameter-documentation gap.

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?

An output schema exists, so return values need not be explained, and the read-only nature is covered by annotations. However, for a tool requiring two opaque identifiers with 0% schema coverage, the description should clarify the run-to-trade relationship and what happens when IDs are invalid.

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%, so the description carries the full burden, yet it never explains what runId or tradeId are beyond a vague '선택한 가상 체결'. The regex patterns exist in the schema but their meaning (24-hex backtest run vs. 'trade-N' identifier) is never stated.

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 (선택한 가상 체결) and enumerates the exact fields returned: signal date, price, quantity, cost, and recorded trade rationale. This is far more specific than the title alone, though it never names or contrasts a sibling tool.

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?

The word '선택한' implies the agent must already have selected a specific fill, but there is no explicit when-to-use statement, no prerequisite (e.g. 'call after meritz_backtest_run'), and no mention of when to prefer meritz_backtest_compare or other siblings.

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