Skip to main content
Glama
Sign In
krds-a11y-mcp

krds-a11y-mcp

by kim-dongho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

SPA 프레임워크 × 킷 충돌 가이드

get_framework_guide
Read-onlyIdempotent

Get fixes for Korea Government Design System widget conflicts in React and Next.js SPAs, including initialization and client-routing issues; omit the framework to list options.

Instructions

React·Next.js에서 킷을 쓸 때의 충돌(킷 JS는 DOMContentLoaded 1회 init·클라이언트 라우팅 모름)과 실사용 검증된 처방을 반환한다. 킷 위젯(탭·아코디언·GNB)이 SPA에서 동작하지 않으면 자체 해법을 발명하기 전에 이 가이드를 먼저 보라. 위젯별 상태 클래스·초기화 함수는 get_component의 '킷 동작' 절에 있다. 반환: 마크다운 — 충돌 원인과 처방(코드 포함). framework 없이 부르면 고를 수 있는 목록.

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": "get_framework_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameworkNo프레임워크 — react(Vite 등 SPA 공통) 또는 nextjs. 비우면 목록을 안내한다

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The readOnly/idempotent annotations already cover the safety profile, yet the description still adds useful behavior: the return is markdown containing cause-and-prescription with code, and omitting framework yields a selectable list instead of an error. Nothing contradicts the annotations; only minor traits (version/scope of the prescriptions) are left unstated.

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

Conciseness5/5

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

Roughly four dense sentences, each with a distinct job: what it returns, when to reach for it, where the related detail lives, and the exact return shape. The core purpose is front-loaded and there is no filler.

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?

No output schema exists, but the description compensates by naming the return format (markdown with code) and the no-argument fallback. With the single optional parameter fully documented, an agent has everything needed to call this correctly on the first attempt.

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%, including the enum meanings and the '비우면 목록' behavior, so the schema already carries the parameter semantics. The description restates the empty-argument fallback but adds no syntax or scoping detail beyond what the schema documents, making the baseline 3 correct.

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: returns a conflict guide for using the kit in React/Next.js, naming the concrete failure mode (kit JS initializes once on DOMContentLoaded and is unaware of client routing). It explicitly hands off a neighboring responsibility to get_component's '킷 동작' section, so an agent can tell the two apart 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 an explicit trigger ('킷 위젯(탭·아코디언·GNB)이 SPA에서 동작하지 않으면') and an explicit ordering rule ('자체 해법을 발명하기 전에 이 가이드를 먼저 보라'). It also names the alternative destination for per-widget details, so routing in both directions is covered.

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

Deploy Server

Other Tools