Skip to main content
Glama

FarmTempo

calculate_margin_bulk

Read-onlyIdempotent

여러 품목의 매입·판매 행을 일괄로 계산해 행별·총계 결과를 반환합니다. HTML 원가율 계산기 탭의 calcRow + totals 와 동일 출력.

Body 스키마

{"rows": [{"item": "배추", "buyPrice": 1000, "sellPrice": 1500, "qty": 1}]}

Returns per-row + aggregated totals for bulk margin calculation.

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": {
      "rows": "<rows>"
    },
    "name": "calculate_margin_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes품목별 매입·판매 행

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds a useful trust signal by claiming output parity with the HTML 원가율 계산기 calcRow + totals. It says nothing about validation failures (qty/sellPrice exclusiveMinimum violations), rounding of currency values, or how missing rows are handled, so beyond the parity claim it adds little.

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?

The purpose is front-loaded in the first Korean sentence and the embedded body example is compact and directly usable. The closing English sentence largely repeats the opening claim ('행별·총계 결과'), which is mild redundancy but not disruptive.

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?

Annotations and an output schema mean the description needn't explain return values, and it correctly points to output parity with the calculator. What remains unexplained is the core semantics of a calculation tool: whether 'margin' is profit amount or margin rate, how totals aggregate across rows, and what happens on invalid input.

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 coverage is 100% and each nested field carries its own description and units (원, 수량 기본 1), so the schema does the heavy lifting and baseline 3 applies. The inline JSON body example restates the schema structure with sample values rather than adding new semantics such as how totals are derived from buyPrice/sellPrice/qty.

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?

The description states a specific verb and resource (일괄 계산, 매입·판매 행) plus the output shape (행별·총계), which separates it from a single-item calculator. The contrast with the sibling calculate_margin is only implied by '여러 품목' / 'bulk' rather than stated, so an agent must infer the boundary.

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?

'일괄로' and '여러 품목' imply usage for multi-row batches, and the inline body example shows the expected call shape. However, there is no explicit statement of when to pick this over calculate_margin, no prerequisites (e.g., items needing resolution first), and no exclusions such as row-count limits.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources