Migrate Dependabot toolset to modelcontextprotocol/go-sdk

[Copilot]

Closes #<issue_number>

Migrates the Dependabot toolset from mark3labs/mcp-go to modelcontextprotocol/go-sdk, enabling two tools:

• get_dependabot_alert - Retrieves a specific Dependabot alert by number
• list_dependabot_alerts - Lists Dependabot alerts with optional state/severity filters

Key Changes

Function signatures:

// Before
func GetDependabotAlert(...) (tool mcp.Tool, handler server.ToolHandlerFunc)

// After  
func GetDependabotAlert(...) (mcp.Tool, mcp.ToolHandlerFor[map[string]any, any])

Handler implementation:

• Updated from func(ctx, request) (*result, error) to func(ctx, *request, args) (*result, any, error)
• Parameter extraction now uses args map[string]any instead of mcp.CallToolRequest
• Result helpers migrated from mcp.NewToolResult* to utils.NewToolResult*

Schema definitions:

• Converted from DSL-based (mcp.WithString(...)) to JSON Schema structures (jsonschema.Schema)
• Default values now use json.RawMessage for proper serialization

Toolsnaps:

• Field ordering changes (annotations, schema properties) with no semantic differences

Original prompt

Migrate the Dependabot toolset to the Go SDK.

Migration Process

You should focus on ONLY the toolset I have requested and it's corresponding test file. If, for example, you are asked to migrate the dependabot toolset, you will be migrating the files located at .tools-to-be-migrated/dependabot.go and .tools-to-be-migrated/dependabot_test.go. The migrated version should be placed in the github package directory, pkg/github (e.g. pkg/github/dependabot.go and pkg/github/dependabot_test.go). If there are additional tests or helper functions that fail to work with the new SDK, you should inform me of these issues so that I can address them, or instruct you on how to proceed.

When generating the migration guide, consider the following aspects:

• The initial tool file and it's corresponding test file will be fully commented out, as the tests will fail if the code is uncommented. The code should be uncommented before work begins.
• The import for github.com/mark3labs/mcp-go/mcp should be changed to github.com/modelcontextprotocol/go-sdk/mcp
• The return type for the tool constructor function should be updated from mcp.Tool, server.ToolHandlerFunc to (mcp.Tool, mcp.ToolHandlerFor[map[string]any, any]).
• The tool handler function signature should be updated to use generics, changing from func(ctx context.Context, mcp.CallToolRequest) (*mcp.CallToolResult, error) to func(context.Context, *mcp.CallToolRequest, map[string]any) (*mcp.CallToolResult, any, error).
• The RequiredParam, RequiredInt, RequiredBigInt, OptionalParamOK, OptionalParam, OptionalIntParam, OptionalIntParamWithDefault, OptionalBoolParamWithDefault, OptionalStringArrayParam, OptionalBigIntArrayParam and OptionalCursorPaginationParams functions should be changed to use the tool arguments that are now passed as a map in the tool handler function, rather than extracting them from the mcp.CallToolRequest.
• mcp.NewToolResultText, mcp.NewToolResultError, mcp.NewToolResultErrorFromErr and mcp.NewToolResultResource no longer available in modelcontextprotocol/go-sdk. There are a few helper functions available in pkg/utils/result.go that can be used to replace these, in the utils package.

Schema Changes

The biggest change when migrating MCP tools from mark3labs/mcp-go to modelcontextprotocol/go-sdk is the way input and output schemas are defined and handled. In mark3labs/mcp-go, input and output schemas were often defined using a DSL provided by the library. In modelcontextprotocol/go-sdk, schemas are defined using jsonschema.Schema structures using github.com/google/jsonschema-go, which are more verbose.

When migrating a tool, you will need to convert the existing schema definitions to JSON Schema format. This involves defining the properties, types, and any validation rules using the JSON Schema specification.

Example Schema Guide

If we take an example of a tool that has the following input schema in mark3labs/mcp-go:

...
return mcp.NewTool(
		"list_dependabot_alerts",
		mcp.WithDescription(t("TOOL_LIST_DEPENDABOT_ALERTS_DESCRIPTION", "List dependabot alerts in a GitHub repository.")),
		mcp.WithToolAnnotation(mcp.ToolAnnotation{
			Title:        t("TOOL_LIST_DEPENDABOT_ALERTS_USER_TITLE", "List dependabot alerts"),
			ReadOnlyHint: ToBoolPtr(true),
		}),
		mcp.WithString("owner",
			mcp.Required(),
			mcp.Description("The owner of the repository."),
		),
		mcp.WithString("repo",
			mcp.Required(),
			mcp.Description("The name of the repository."),
		),
		mcp.WithString("state",
			mcp.Description("Filter dependabot alerts by state. Defaults to open"),
			mcp.DefaultString("open"),
			mcp.Enum("open", "fixed", "dismissed", "auto_dismissed"),
		),
		mcp.WithString("severity",
			mcp.Description("Filter dependabot alerts by severity"),
			mcp.Enum("low", "medium", "high", "critical"),
		),
	),
...

The corresponding input schema in modelcontextprotocol/go-sdk would look like this:

...
return mcp.Tool{
  Name: "list_dependabot_alerts",
  Description: t("TOOL_LIST_DEPENDABOT_ALERTS_DESCRIPTION", "List dependabot alerts in a GitHub repository."),
  Annotations: &mcp.ToolAnnotations{
    Title: t("TOOL_LIST_DEPENDABOT_ALERTS_USER_TITLE", "List dependabot alerts"),
    ReadOnlyHint: true,
  },
  InputSchema: &jsonschema.Schema{
    Type: "object",
    Properties: map[string]*jsonschema.Schema{
      "owner": {
        Type: "string",
        Description: "The owner of the repository.",
      },
      "repo": {
        Type: "string",
        Description: "The name of the repository.",
      },
      "state": {
        Type: "string",
        Description: "Filter dependabot alerts by state. Defaults to open",
        Enum: []string{"open", "fixed", "dismissed", "auto_dismissed"},
        Default: "open",
      },
      "severity": {
        Type: "string",
        Description: "Filter dependabot alerts by severity",
        Enum: []string{"low", "medium"...

</details>



<!-- START COPILOT CODING AGENT TIPS -->
---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more [Copilot coding agent tips](https://gh.io/copilot-coding-agent-tips) in the docs.