Skip to main content
Glama

투표함 — 전자투표 법령 자료 (Korean e-voting statutes, quorum & consult)

맞춤 투표함 상담 신청

request_consult

업체(운영자)가 명부 정리·개설·집계를 대신하는 맞춤 투표함(1인당 300원)을 신청한다. 담당자가 연락한다. 담당자 이름·연락처가 필요하다. 사람에게 연락이 가는 행동이다 — 주최자가 원할 때만. 직접 열려면 사이트의 직접 투표함(/w/new.html)으로 안내한다.

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": {
      "orgName": "<orgName>",
      "contactName": "<contactName>",
      "contactPhone": "<contactPhone>"
    },
    "name": "request_consult"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNo요청 내용(2,000자까지). 집회일·안건·명부 상태 등
orgNameYes단체 이름. 예: "한빛타워 관리단"
orgTypeNo단체 유형 키(선택). 예: "bldg"
headCountNo투표 예정 인원(선택). 예: 366
contactNameYes담당자 이름. 예: "홍길동"
contactEmailNo담당자 이메일(선택). 예: "manager@example.com"
contactPhoneYes담당자 휴대폰(숫자·하이픈). 예: "010-1234-5678"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / contactName / description
      Previous value: -"담당자 이름. 예: \"김기용\""New value: +"담당자 이름. 예: \"홍길동\""
    • changedInput schema / properties / orgName / description
      Previous value: -"단체 이름. 예: \"트레젠웰가 관리단\""New value: +"단체 이름. 예: \"한빛타워 관리단\""
  2. Changed7 schema fields changed
    • addedInput schema / properties / contactEmail / description
      Added value: +"담당자 이메일(선택). 예: \"manager@example.com\""
    • addedInput schema / properties / contactName / description
      Added value: +"담당자 이름. 예: \"김기용\""
    • addedInput schema / properties / contactPhone / description
      Added value: +"담당자 휴대폰(숫자·하이픈). 예: \"010-1234-5678\""
    • addedInput schema / properties / headCount / description
      Added value: +"투표 예정 인원(선택). 예: 366"
    • addedInput schema / properties / message / description
      Added value: +"요청 내용(2,000자까지). 집회일·안건·명부 상태 등"
    • addedInput schema / properties / orgName / description
      Added value: +"단체 이름. 예: \"트레젠웰가 관리단\""
    • addedInput schema / properties / orgType / description
      Added value: +"단체 유형 키(선택). 예: \"bldg\""
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only state readOnly=false, destructive=false, openWorld=false, idempotent=false. The description adds real context beyond them: a human follow-up contact is triggered, a price of 300원 per person applies, and contact name/phone are mandatory. It does not say what happens on repeat submissions (relevant given idempotentHint=false) or what response the caller gets.

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?

Four short sentences, front-loaded with the purpose before the cost, contact requirement, and alternative path. Nearly every sentence earns its place; the required-contact sentence is the only mild overlap with the 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 non-idempotent submission tool with no output schema, the description covers who does the work, the price, the human follow-up, and the alternative route. It leaves slightly open whether payment is collected at submission time and what confirmation the caller receives.

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% with examples for every property, so the schema already carries parameter meaning. The description only restates that 담당자 이름·연락처 are required, which duplicates the required array and adds no new semantics.

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 uses a concrete verb-plus-object ('맞춤 투표함... 신청한다') and immediately explains what the operator does on the applicant's behalf (명부 정리·개설·집계). It also distinguishes this assisted path from self-service by pointing at the direct-ballot page (/w/new.html), though it does not differentiate against the listed sibling tools.

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

Usage Guidelines5/5

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

It gives an explicit trigger condition ('사람에게 연락이 가는 행동이다 — 주최자가 원할 때만') and a concrete when-not with the alternative path ('직접 열려면... /w/new.html'). An agent can decide between assisted and self-service without further inference.

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