Skip to main content
Glama

APICK Business

현금영수증 소득공제 내역 인증 요청

req_cash_receipt_deduction

현금영수증 소득공제 내역을 위한 본인 간편인증을 요청합니다. 휴대폰 알림 발송과 접수 과금이 발생하므로 사용자 확인 후 호출하세요. transactionId와 status를 반환하면 휴대폰 승인을 안내하고, 승인 후 get_cash_receipt_deduction에 transactionId를 전달하세요. 승인 대기 중 인증 요청을 반복하거나 자동 승인하지 마세요. [인증 발송 성공 시 20P; 조회 범위와 무관]

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": {
      "name": "<name>",
      "birthDate": "<birthDate>",
      "phone": "<phone>",
      "authProvider": "<authProvider>"
    },
    "name": "req_cash_receipt_deduction"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes본인 이름
phoneYes본인 명의 휴대전화 번호 (숫자만)
telcoNo통신사 코드. authProvider=pass(통신사 PASS)일 때 필수이며, 빠지거나 허용값이 아니면 인증 요청 없이 400으로 거절합니다. S SKT·K KT·L LGU+·SA SKT알뜰폰·KA KT알뜰폰·LA LGU+알뜰폰
birthDateYes생년월일 8자리 (YYYYMMDD)
incomeYearsNo소득공제 조회 연수 (1~3, 생략 시 1)
authProviderYes휴대폰에서 승인할 간편인증 방식

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / telco / description
      Previous value: -"통신사 코드 (authProvider=pass(통신사 PASS)일 때만 필수: S SKT·K KT·L LGU+·SA SKT알뜰폰·KA KT알뜰폰·LA LGU+알뜰폰)"New value: +"통신사 코드. authProvider=pass(통신사 PASS)일 때 필수이며, 빠지거나 허용값이 아니면 인증 요청 없이 400으로 거절합니다. S SKT·K KT·L LGU+·SA SKT알뜰폰·KA KT알뜰폰·LA LGU+알뜰폰"
  2. Changed1 schema field changed
    • addedInput schema / properties / telco
      Added value: +{
      +  "description": "통신사 코드 (authProvider=pass(통신사 PASS)일 때만 필수: S SKT·K KT·L LGU+·SA SKT알뜰폰·KA KT알뜰폰·LA LGU+알뜰폰)",
      +  "enum": [
      +    "S",
      +    "K",
      +    "L",
      +    "SA",
      +    "KA",
      +    "LA"
      +  ],
      +  "type": "string"
      +}
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false): it discloses that a push notification is dispatched to the user's phone, that a 20P charge is incurred on successful dispatch regardless of query scope, and that the call is asynchronous and returns transactionId plus status pending user approval. The warning against repeating requests directly operationalizes the non-idempotent hint, which annotations alone would not convey.

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?

Front-loaded with purpose, then the cost/caution, then the approval flow, then prohibitions — a sensible ordering with no filler sentences. Minor redundancy between '접수 과금이 발생' and the trailing '[인증 발송 성공 시 20P]' note, which restates the same billing fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 supplies the return contract (transactionId and status) and the full two-step flow through get_cash_receipt_deduction. For a 6-parameter, non-idempotent authentication-initiation tool, nothing an agent needs to call it safely is missing.

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 each parameter, including the telco/authProvider enums and the 400 rejection behavior for a missing telco, is already documented in the schema. The description adds no additional meaning about name, birthDate, phone, telco, authProvider, or incomeYears, so the 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?

States a specific verb and resource ('현금영수증 소득공제 내역을 위한 본인 간편인증을 요청합니다') and explicitly names the counterpart tool get_cash_receipt_deduction that consumes the resulting transactionId, so an agent can separate the request step from the retrieval step without opening either schema.

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?

Gives explicit preconditions ('사용자 확인 후 호출하세요'), the downstream step after the call ('승인 후 get_cash_receipt_deduction에 transactionId를 전달하세요'), and explicit prohibitions ('승인 대기 중 인증 요청을 반복하거나 자동 승인하지 마세요'). When-to-use, when-not-to-use, and the alternative path are all present.

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.