Skip to main content
Glama

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

전자투표 가능 여부

electronic_voting_basis
Read-onlyIdempotent

이 안건을 전자투표로 할 수 있는가 — 법이 직접 허용 / 규약·정관 근거 필요 / 불가(전자서명 요구 등) — 와 그 근거 조문.

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": {
      "key": "<key>"
    },
    "name": "electronic_voting_basis"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes안건 유형 키. 예: "coop_special", "agm_ordinary"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / key / description
      Previous value: -"안건 유형 키. 예: \"coop_bylaw\", \"stock_ordinary\""New value: +"안건 유형 키. 예: \"coop_special\", \"agm_ordinary\""
  2. Changed1 schema field changed
    • addedInput schema / properties / key / description
      Added value: +"안건 유형 키. 예: \"coop_bylaw\", \"stock_ordinary\""
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish this is a safe, idempotent, closed-world read, so the bar is lower. The description adds genuinely useful behavioral context absent from annotations: the response is a three-way determination (statute-permitted / requires rules or articles basis / not allowed, e.g. e-signature required) together with the cited provisions.

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

Conciseness5/5

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

One compact sentence, front-loaded with the core question and then the enumerated outcomes, followed by the citation note. No filler, no repetition of the title.

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 one-parameter read-only lookup with no output schema, the description covers both the decision space and the return contents (classification plus 근거 조문). A minor gap is not indicating how the cited provisions relate to get_statute, which would help an agent chain calls.

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?

There is a single required 'key' parameter with 100% schema description coverage and concrete examples ("coop_special", "agm_ordinary"). The description only implies that this key identifies the agenda type; it adds no format, naming, or fallback guidance beyond the schema, so the baseline 3 applies.

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 question the tool answers (whether an agenda item may use electronic voting) and enumerates the three possible classifications plus the supporting statutory basis. It is far more specific than the name alone, but it never names or contrasts itself with related siblings such as get_resolution_requirement or judge_resolution.

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: the agent should call this when it needs to know if e-voting is lawful for a given agenda type. There is no explicit when-to-use/when-not-to-use framing and no routing to alternatives like get_resolution_requirement when the real question is quorum or majority.

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