Skip to main content
Glama

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

요금 견적

get_quote
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": {
      "people": "<people>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
peopleYes투표할 수 있는 사람 수. 예: 366

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / people / description
      Added value: +"투표할 수 있는 사람 수. 예: 366"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context — the figures include VAT — but '아무것도 바꾸지 않는다' merely restates the readOnly hint. It says nothing about the shape of the returned quote, which matters because there is no output schema.

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?

Three short sentences, front-loaded with the calculation and its output scope, with no filler. The final sentence is close to redundant with the annotations, which is the only thing keeping it from a 5.

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?

For a one-parameter, non-destructive calculator this covers the input side well. Because there is no output schema, the description carries the burden of describing the return value, and '두 갈래 … 요금' only gestures at the two-tier result without saying what a quote contains (per-tier prices, breakdown, totals).

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% and the single parameter 'people' is fully documented with an example, so the description cannot add much. It does confirm the parameter means the voting population being priced, and it introduces the two-tier output notion that the schema lacks. 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?

States a specific verb (계산한다) and resource (요금) and adds the decisive scope detail that it prices two product tiers from a voter count. An agent can tell it is the pricing tool among law/statute/resolution siblings, though it never names or contrasts those siblings explicitly.

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: call it when you need a cost estimate for a given number of voters. There is no explicit when-to-use framing, no prerequisites, and no mention of what to do instead when a quote is not what is needed.

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