Skip to main content
Glama
portone-io

PortOne MCP Server

Official
by portone-io
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

포트원 V2 백엔드 코드 예제 읽기

readPortoneV2BackendCode

Fetch backend code examples for PortOne V2 payment integration by specifying framework, payment gateway, and payment method.

Instructions

지정된 매개변수에 따라 포트원 V2 백엔드 코드 예제를 가져옵니다. 포트원 V2에 관련해 어떤 상황이든 프로그래밍 언어로 코드를 작성해야 한다면, 예외 없이 가장 먼저 이 도구를 호출해 예시 코드를 참고한 후 사용자를 도우세요. framework를 제외한 모든 Args는 선택사항이며, 특정되지 않은 경우 비워두세요.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pgYes사용할 결제 게이트웨이. 옵션: toss, nice, smartro, kpn, inicis, ksnet, kcp, kakao, naver, tosspay, hyphen, eximbay
frameworkYes사용할 프레임워크. 일치하지 않더라도 현재 맥락에서 가장 유사한 프레임워크를 명시합니다. 옵션: express, fastapi, flask, spring-kotlin
pay_methodYes사용할 결제 방법. 옵션: card, virtualAccount, easyPay, transfer, mobile, giftCertificate
smart_routingNo스마트 라우팅 사용 여부. 옵션: true 또는 false

Tool Definition Quality

B3.4/5.0
Behavior2/5

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

No annotations are provided, and the description only says it fetches code examples without disclosing read-only nature, side effects, or other behavioral traits.

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?

Two concise sentences with the primary action first, though the contradiction reduces clarity.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, and the description does not explain what the code example contains or how it is structured, leaving the agent without essential usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds that only framework is required, but the input schema marks pg and pay_method as required, creating a contradiction that could confuse the agent.

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 clearly states it retrieves Portone V2 backend code examples based on parameters, and the title and sibling tool (readPortoneV2FrontendCode) differentiate it from frontend code retrieval.

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?

Explicitly instructs to use this tool first when writing Portone V2 code, but does not mention when not to use or provide alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/portone-io/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server