data-api-builder-mcp-mastery

스타8

포크6

업데이트2026년 5월 13일 01:42

Polish Data API Builder SQL MCP Server surfaces with descriptions, curated tools, and role-gated DML for reliable agent use.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

JerryNixon

JerryNixon/data-api-builder-vscode-ext

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Data API Builder MCP Mastery

Use when

An existing MCP endpoint works but agents pick wrong tools or hallucinate parameters.
Tightening the tool surface: hiding entities and exposing curated stored procedures as custom tools.
Hardening DML so writes only run under authenticated roles.

Workflow

Set runtime.mcp.description; DAB sends it as MCP instructions during initialization.
Add entity.description and fields[] entries with name, description, and primary-key where needed.
For stored procedures, describe the entity and source.parameters[] (name, description, required, default).
Prune with runtime.mcp.dml-tools globally and entity mcp.dml-tools: false locally.
For curated stored procedures, set entity mcp.custom-tool: true so the procedure appears as a named tool.
Validate with MCP Inspector: tool list, describe_entities, CRUD operations, and stored-procedure calls.

Guardrails

Descriptions flow through describe_entities; missing fields[] metadata can leave agents with empty field arrays.
DAB intentionally does not support NL2SQL; don't try to bolt it on — expose deterministic tools instead.
Per-tool toggles exist only under runtime.mcp.dml-tools; entity mcp is a gate, not per-tool CRUD control.
Entity RBAC, field include/exclude rules, and policies apply through MCP; hidden fields stay hidden.
Avoid anonymous writes; if unauthenticated access is required, grant the narrowest read/execute actions.

Related skills

data-api-builder-mcp
data-api-builder-config
data-api-builder-auth
aspire-mcp-inspector
azure-mcp-inspector

Microsoft Learn

이 저장소의 다른 Skills

같은 저장소

azure-sql-commander

JerryNixon/data-api-builder-vscode-ext

Run SQL Commander as a companion container for browser-based SQL access, with optional Azure Container Apps configuration.

2026-07-148

aspire-data-api-builder

JerryNixon/data-api-builder-vscode-ext

Orchestrate SQL Server and Data API Builder with .NET Aspire for local development, health-aware startup, and dashboard-driven diagnostics.

2026-05-138

aspire-mcp-inspector

JerryNixon/data-api-builder-vscode-ext

Add MCP Inspector to .NET Aspire AppHost for local SQL MCP Server validation and tool discovery.

2026-05-138

aspire-sql-commander

JerryNixon/data-api-builder-vscode-ext

Add SQL Commander to .NET Aspire for lightweight SQL browsing and query execution during local DAB development.

2026-05-138

aspire-sql-projects

JerryNixon/data-api-builder-vscode-ext

Use SQL Database Projects (.sqlproj) with .NET Aspire for declarative schema deployment via dacpac.

2026-05-138

azure-app-service-data-api-builder

JerryNixon/data-api-builder-vscode-ext

Deploy Data API Builder and SQL MCP Server to Azure App Service for Linux, with or without containers.

2026-05-138

name	data-api-builder-mcp-mastery
description	Polish Data API Builder SQL MCP Server surfaces with descriptions, curated tools, and role-gated DML for reliable agent use.
license	MIT

Data API Builder MCP Mastery

Use when

An existing MCP endpoint works but agents pick wrong tools or hallucinate parameters.
Tightening the tool surface: hiding entities and exposing curated stored procedures as custom tools.
Hardening DML so writes only run under authenticated roles.

Workflow

Set runtime.mcp.description; DAB sends it as MCP instructions during initialization.
Add entity.description and fields[] entries with name, description, and primary-key where needed.
For stored procedures, describe the entity and source.parameters[] (name, description, required, default).
Prune with runtime.mcp.dml-tools globally and entity mcp.dml-tools: false locally.
For curated stored procedures, set entity mcp.custom-tool: true so the procedure appears as a named tool.
Validate with MCP Inspector: tool list, describe_entities, CRUD operations, and stored-procedure calls.

Guardrails

Descriptions flow through describe_entities; missing fields[] metadata can leave agents with empty field arrays.
DAB intentionally does not support NL2SQL; don't try to bolt it on — expose deterministic tools instead.
Per-tool toggles exist only under runtime.mcp.dml-tools; entity mcp is a gate, not per-tool CRUD control.
Entity RBAC, field include/exclude rules, and policies apply through MCP; hidden fields stay hidden.
Avoid anonymous writes; if unauthenticated access is required, grant the narrowest read/execute actions.

Related skills

data-api-builder-mcp
data-api-builder-config
data-api-builder-auth
aspire-mcp-inspector
azure-mcp-inspector