Skip to main content
Glama

하이패스 미납 여부 조회

hipass_unpaid
Read-only

Check whether a Korean vehicle has unpaid expressway (Hi-pass) tolls by plate number. 차량번호로 고속도로 통행료 미납 대상 여부와 미납 건수를 조회합니다. 미납이 없어도(unpaid_target=false) 정상 조회로 과금됩니다. 미납 금액·통행 내역은 제공하지 않습니다. [호출당 60포인트]

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": {
      "car_no": "<car_no>"
    },
    "name": "hipass_unpaid"
  }
}

Input Schema

NameRequiredDescriptionDefault
car_noYes차량번호. 예: 12가3456, 서울12가3456

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnly/openWorld, the description discloses the cost model (60 points per call), the billing edge case (charged even when unpaid_target=false), and the absence of amount/history data. This tells the agent how the call behaves in a way the annotations do not.

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 English purpose line is front-loaded, followed by the return content, the billing caveat, and the cost. Every sentence carries information, though the Korean restatement of the purpose partially duplicates the English sentence.

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?

With no output schema, the description compensates by naming the returned signals (unpaid_target flag, unpaid count) and what is out of scope. It omits failure modes, such as how an invalid or unregistered plate is reported, which is a small remaining gap for a read-only lookup.

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 parameter at 100% schema coverage, and the schema already supplies the format and examples (12가3456, 서울12가3456). The description only restates that lookup is by plate number, adding little semantic detail beyond the schema; baseline 3 applies.

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?

The description states a specific verb and resource (check unpaid expressway/Hi-pass tolls) and a precise scope (Korean vehicle, by plate number). It also distinguishes itself from near-neighbours by declaring what it does not return: unpaid amounts and toll history.

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?

It gives clear invocation context and an important exclusion: use it for presence/count only, not for amount or trip detail. It also warns that every call is billed even when nothing is unpaid. What is missing is an explicit alternative to call when the agent actually needs amounts or history.

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.