'tool-design' 검색 결과

REA 조사 도구를 설계하거나 변경할 때 담당 범위, 입출력, CLI 및 MCP 호출 규칙을 정리합니다. 조사 근거의 의미와 검증 방법을 포함한 설계안을 작성합니다.

• 새로운 REA 조사 도구 설계
• CLI 및 MCP 입출력 검토
• provider 책임과 Evidence 의미 정리

Design tools that AI agents can choose and use correctly. Define clear descriptions, inputs, and outputs, manage large search results, and plan approval checks, isolated execution environments, and interfaces for collaboration between agents.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing the scope of tools for an MCP server
• Improving tool descriptions and input examples
• Designing pagination and truncation for search results

Plan and build an MCP server, a connection that lets Claude use external tools. Choose hosting, tool structure, authentication, and a framework, then scaffold a server or hand off to specialized packaging and interface skills.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Connect a cloud API to Claude
• Choose how to run and distribute an MCP server
• Organize tools for an API with many actions

Design tools that agents can select and call correctly. Clarify descriptions, input rules, response formats, and recovery messages, then review overlapping tools and naming conventions using examples of successful and failed calls.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing descriptions and input rules for new tools
• Investigating incorrect tool selection and calls
• Improving error messages with recovery steps

Plan projects that use large language models, from checking whether the task suits a model to designing processing stages. Estimate costs, choose single or multiple agents, and organize prototypes, structured outputs, and iteration.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking whether a task is suitable for an LLM
• Designing a pipeline for batch analysis
• Estimating processing costs before development

Designing side-by-side comparison tools (plan-compare, product-compare, alternative-compare) that help users decide rather than just listing features. Axis selection, default-comparison logic, recommendation discipline. Honest about feature-list-dump (every feature in a row, no decision support), hidden-recommendation (biased comparison pretending to be neutral), and honest-comparison-with-guidance (genuine comparison plus opinionated recommendation) patterns. Triggers on comparison tool, plan compare, product compare, alternative compare, vs page, decision support tool. Also triggers when conversion through comparison stages is poor, when users are abandoning at the comparison step, or when a comparison tool is being scoped for the first time.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build MCP tools that are sticky for vibe coders and powerful for developersUse when "Designing new MCP tools, Improving tool UX or DX, Writing error messages, Planning tool naming, Discussing user onboarding, Making tools "sticky", Vibe coder experience, mcp, product, ux, dx, vibe-coding, onboarding, developer-experience, tool-design" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze an arbitrary codebase to identify functions, APIs, and data sources suitable for exposure as MCP tools, producing a tool specification document. Use when planning an MCP server for an existing project, auditing a codebase before wrapping it as an AI-accessible tool surface, comparing what a codebase can do versus what is already exposed via MCP, or generating a tool spec to hand off to scaffold-mcp-server.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The Agent Tool Contract — 5 principles for designing tools agents call reliably: predictable signature, rich errors, token-efficient output, idempotency, graceful degradation. Includes anti-pattern table with 8 common mistakes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design tools that agents can use effectively, including when to reduce tool complexity. Use when creating, optimizing, or reducing agent tool sets.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill should be used when the user asks to "design agent tools", "create tool descriptions", "reduce tool complexity", "implement MCP tools", or mentions tool consolidation, architectural reduction, tool naming conventions, or agent-tool interfaces.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build tools that agents can use effectively, including architectural reduction patterns. Use when creating new tools for agent systems, debugging tool-related failures or misuse, or optimizing existing tool sets for better agent performance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.