Skip to main content
Glama
burkeholland

VS Code MCP Button Generator

by burkeholland

Copilot install buttons (GitHub)

copilot_buttons_from_github

Create VS Code install buttons for GitHub files by specifying owner, repository, and file path. Generates markdown badges for MCP server installation.

Instructions

Generate VS Code install buttons for a GitHub file using owner/repo/path and optional branch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesInstall kind
ownerYes
repoYes
pathYesPath within the repo
branchNomain

Implementation Reference

  • src/index.ts:166-183 (registration)
    Registers the MCP tool 'copilot_buttons_from_github' with Zod input schema and a handler that delegates to the helper function.
    server.registerTool(
      "copilot_buttons_from_github",
      {
        title: "Copilot install buttons (GitHub)",
        description: "Generate VS Code install buttons for a GitHub file using owner/repo/path and optional branch.",
        inputSchema: {
          kind: z.enum(["chat-instructions", "chat-prompt", "chat-mode"]).describe("Install kind"),
          owner: z.string(),
          repo: z.string(),
          path: z.string().describe("Path within the repo"),
          branch: z.string().default("main"),
        }
      },
      async ({ kind, owner, repo, path, branch }) => {
        const markdown = generateCopilotInstallButtonsFromGithub(kind, owner, repo, path, branch ?? 'main');
        return { content: [{ type: "text", text: markdown }] };
      }
    );
  • The core handler logic: constructs the raw GitHub URL for the file and generates the Copilot-style install buttons markdown.
    export function generateCopilotInstallButtonsFromGithub(kind: CopilotInstallKind, owner: string, repo: string, path: string, branch = 'main'): string {
      const raw = buildRawGithubUrl(owner, repo, branch, path);
      return generateCopilotInstallButtons(kind, raw);
    }
  • Zod input schema definition for the tool parameters.
    inputSchema: {
      kind: z.enum(["chat-instructions", "chat-prompt", "chat-mode"]).describe("Install kind"),
      owner: z.string(),
      repo: z.string(),
      path: z.string().describe("Path within the repo"),
      branch: z.string().default("main"),
    }
  • Helper function to build the raw GitHub file URL from repo details.
    export function buildRawGithubUrl(owner: string, repo: string, branch: string, path: string): string {
      return `https://raw.githubusercontent.com/${owner}/${repo}/${branch}/${path}`;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions generating install buttons but lacks details on what these buttons do (e.g., install Copilot extensions, trigger actions), the output format (e.g., HTML, markdown), any rate limits, authentication needs, or side effects. This leaves significant gaps for an agent to understand the tool's behavior.

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?

The description is a single, efficient sentence that front-loads the core purpose ('Generate VS Code install buttons') and includes essential parameter information without unnecessary details. Every word contributes directly to the tool's functionality, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (5 parameters, 40% schema coverage, no output schema, and no annotations), the description is incomplete. It doesn't explain the output (what the generated buttons look like or how to use them), lacks behavioral context, and leaves key parameters underspecified, making it inadequate for an agent to fully understand the tool's operation.

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 40% (only 'kind' and 'path' have descriptions), and the description adds minimal semantic value by listing parameters ('owner/repo/path and optional branch') without explaining their roles or relationships. It doesn't clarify what 'kind' enums represent or how 'branch' defaults to 'main', leaving parameters partially undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Generate VS Code install buttons') and target resource ('for a GitHub file'), with specific identifiers ('using owner/repo/path and optional branch'). However, it doesn't explicitly differentiate from sibling tools like 'copilot_buttons_from_raw' or 'make_install_buttons', which likely serve similar purposes but with different input sources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus its siblings (e.g., 'copilot_buttons_from_raw' or 'make_install_buttons'), nor does it mention any prerequisites, exclusions, or alternative scenarios. It only states what the tool does without contextual usage advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/burkeholland/mcp-vsc-button-gen'

If you have feedback or need assistance with the MCP directory API, please join our Discord server