Skip to main content
Glama

WOOKANG TECH LED sign quote

우강테크에 전화 상담 신청

submit_inquiry

Send a call-back request to WOOKANG TECH; staff call within 1 business day. Call only after the user gives a real phone number and explicit consent (consent=true). Write action. 문의를 넣기 전에 반드시 사용자에게 "우강테크가 전화 상담을 위해 이 전화번호를 쓰는 것"에 동의하는지 묻고, 동의한 경우에만 consent:true 로 보낸다. 동의 없이 보내면 400 으로 거절된다.

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": {
      "phone": "<phone>",
      "consent": "<consent>"
    },
    "name": "submit_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoOrganization / shop name if the user gave one
phoneYesUser's Korean phone number, mobile preferred (e.g. 010-1234-5678). Landline with area code also accepted.
placeNoindoor or outdoor if known
consentYestrue only if the user explicitly agreed to be called back on this number (개인정보 수집·이용 동의).
width_mNoWidth in meters if known
height_mNoHeight in meters if known
agent_nameNoName of the AI assistant submitting (e.g. "ChatGPT", "Claude")
what_whereNoWhat to display and where, in the user's words (무엇을 어디에). e.g. "학교 정문, 행사 안내"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false), and the description adds genuinely new behavior: it is a write action, staff respond within 1 business day, and submission without consent is rejected with a 400. It does not mention duplicate/retry behavior despite idempotentHint=false, which would have been the last piece.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The core purpose and gating rule are front-loaded, but the consent instruction is stated three times (English sentence, '(consent=true)' clause, then the full Korean paragraph restating it). Bilingual text may be intentional for a Korean-facing service, yet the duplication costs space without adding information.

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 an 8-parameter mutation with no output schema, the description covers purpose, preconditions, SLA, and the failure mode. The one gap is that it never says what a successful call returns (e.g., a confirmation or reference number), which matters since no output schema exists to describe the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns a bump by tying the consent boolean to a concrete failure mode (400 rejection) and framing phone/consent as gating requirements, not just fields. The remaining optional params (org, place, dimensions, agent_name, what_where) gain nothing from the description beyond the schema.

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 ('Send a call-back request to WOOKANG TECH') plus the outcome/SLA ('staff call within 1 business day'). This clearly separates it from the read-only siblings get_company_info, get_price_range, and search_faq without any schema inspection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the precondition: only after the user supplies a real phone number and gives explicit consent (consent=true), and warns that sending without consent returns 400. It gives clear when-to-use context but never names sibling tools or says when to prefer them, so it stops short of a 5.

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