Skip to main content
Glama

자동차 리콜 대상 조회

vehicle_recall
Read-only

Check whether a Korean vehicle is subject to recalls or free repair campaigns by plate number or VIN. 차량번호 또는 차대번호(VIN) 중 하나로 리콜·무상점검수리 대상 여부와 건수, 리콜별 내용·시정 기간을 조회합니다. 리콜 대상이 아니어도(recall_target=false) 정상 조회로 과금됩니다. car_no 와 vin 은 둘 중 하나만 보냅니다. [호출당 60포인트]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vehicle_recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinNo차대번호 17자리. 예: KMHXX00XXXX000000 (car_no 와 함께 보내지 않는다)
car_noNo차량번호. 예: 12가3456, 서울12가3456 (vin 과 함께 보내지 않는다)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and openWorldHint, and the description adds genuinely useful context beyond them: the call is billed at 60 points even when the vehicle is not a recall target (recall_target=false). It also previews what is returned (count, per-recall details, correction period), though it says nothing about authentication or error cases.

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 definition is front-loaded with purpose, then constraints, then cost, so the most decision-relevant facts come first. The English and Korean text mirror each other, which is mildly redundant for an agent but not wasteful of critical space.

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 covers the salient behaviors an agent needs: input exclusivity, return contents, non-target handling, and per-call cost. Only authentication or failure-mode details are absent, which is minor for a read-only lookup tool.

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%, so both parameters and their formats (17-digit VIN, plate number examples) are already documented in the schema. The description only restates the mutual-exclusivity rule that the schema also contains, adding no new meaning.

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 names a specific verb and resource ('Check whether a Korean vehicle is subject to recalls or free repair campaigns') and constrains the lookup keys to plate number or VIN. It is clearly distinguishable from sibling tools like vehicle_emission or vehicle_model_info, which cover different vehicle attributes.

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 states an explicit input rule: send only one of car_no or vin, never both. It does not compare itself to any alternative tool or say when a recall check is the wrong call, so the routing guidance 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.