Skip to main content
Glama

WOOKANG TECH LED sign quote

LED 전광판 예상 금액 범위 계산

get_price_range
Read-onlyIdempotent

LED display (LED 전광판) price range in KRW for a given size: min–max, VAT excluded, installation extra. Same numbers as the wooktech.co.kr price calculator. result="staff_quote" means no amount — quote nothing. Read-only.

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": {
      "width_m": "<width_m>",
      "height_m": "<height_m>"
    },
    "name": "get_price_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoindoor(실내: 강당·로비·실내 무대) or outdoor(옥외: 건물 밖·정문·옥상). If omitted or unclear, the server guesses from what_where (default indoor) and returns place_hint.
width_mYesScreen width in meters (가로, m). e.g. 3.2
height_mYesScreen height in meters (세로, m). e.g. 1.44
what_whereNoOptional: what to show and where, in the user's words (e.g. "학교 정문, 행사 안내"). Used to prefill quote_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the description's job is lighter. It still adds real value by disclosing pricing assumptions (VAT excluded, installation extra) and an important output-handling rule: result="staff_quote" means no amount and nothing should be quoted. It does not explain rounding, validity period, or currency-conversion behavior, keeping it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and pricing caveats are front-loaded in a compact first sentence. The trailing fragments about result="staff_quote" and 'Read-only' are terse to the point of being slightly cryptic, but no sentence is filler.

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?

There is no output schema, so the description must carry return semantics, and it does cover the min–max range, currency, VAT exclusion, installation extra, and the staff_quote sentinel. It leaves quote_url and place_hint handling to the input schema and does not describe the response shape beyond the amount, so a small gap remains.

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 100%, including units (meters, 가로/세로), ranges, and the indoor/outdoor distinction for place, so the schema does the heavy lifting. The description adds only 'for a given size' and no per-parameter meaning beyond that, which is the baseline 3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('price range in KRW for a given size') plus the exact scope of the number (min–max, VAT excluded, installation extra). This is clearly distinguishable from siblings like get_company_info, search_faq, and submit_inquiry, which do not compute estimates.

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 implied by the calculator framing ('Same numbers as the wooktech.co.kr price calculator'), but there is no explicit when-to-use or when-not guidance, e.g. whether to use this before submit_inquiry or how to handle a customer who wants a binding quote. The 'quote nothing' rule for staff_quote is a partial routing instruction, not full guidance.

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