AI Skill Store

register_developer

Register a developer account on AI Skill Store. API key is issued after email verification. / 개발자 계정 등록.
이메일 인증 후 API 키가 발급됩니다 (보안을 위해 즉시 발급되지 않음).

Args:
    username: 사용할 username (영문/숫자, 3자 이상, 중복 불가)
    email: 인증용 이메일 주소 (필수 — 인증 링크가 발송됨)

Returns:
    등록 결과 메시지. 이메일 인증 후 API 키를 받을 수 있습니다.

Input Schema

Name	Required	Description	Default
`email`	Yes	Real email address that will receive the verification link, e.g. dev@example.com. The API key is issued after the link is clicked.
`username`	Yes	Desired unique username: letters and digits only, at least 3 characters, e.g. 'myagentdev'.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

addedInput schema / properties / email / description

Added value: +"Real email address that will receive the verification link, e.g. dev@example.com. The API key is issued after the link is clicked."

addedInput schema / properties / username / description

Added value: +"Desired unique username: letters and digits only, at least 3 characters, e.g. 'myagentdev'."

First observedApr 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive behavior. The description adds important context beyond annotations: the API key is not issued immediately and requires email verification, which is central to understanding the tool's side effects and follow-up flow.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the key behavior, but the English and Korean text substantially duplicate each other, and the Args/Returns blocks repeat information already fully present in the schema and output schema.

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?

For a two-parameter registration tool with full schema coverage and an output schema, the description is mostly complete: it explains the email verification requirement and delayed API key issuance. It could still mention duplicate-account handling or what happens if verification is not completed.

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 the schema already explains both parameters in detail. The description restates username constraints and the email verification purpose, but adds no new syntax or edge-case semantics beyond the schema.

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: 'Register a developer account on AI Skill Store.' It is immediately distinguishable from sibling tools, which are mostly read/upload/vetting utilities rather than account creation.

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 as the onboarding step needed before obtaining an API key, but the description does not explicitly say when to use this versus alternatives, whether an account may already exist, or what prerequisites are required beyond email verification.

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

All AI Skill Store tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?