Skip to main content
Glama

github_copilot_cancel_copilot_seat_assignment_for_teams

Cancel Copilot seat assignments for teams in your organization to reduce subscription usage.

Instructions

Remove teams from the Copilot subscription for an organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgYesorg

Implementation Reference

  • The handler function that executes the tool logic: sends a DELETE request to /orgs/{org}/copilot/billing/selected_teams to remove teams from the Copilot subscription.
    handler: async (args: Record<string, any>) => {
      return githubRequest("DELETE", `/orgs/${args.org}/copilot/billing/selected_teams`, undefined, undefined);
    },
  • Input schema for the tool: requires a single 'org' string parameter.
    inputSchema: z.object({
      org: z.string().describe("org")
    }),
  • Tool definition registered as part of the copilotTools array in src/tools/copilot.ts.
    {
      name: "github_copilot_cancel_copilot_seat_assignment_for_teams",
      description: "Remove teams from the Copilot subscription for an organization",
      inputSchema: z.object({
        org: z.string().describe("org")
      }),
      handler: async (args: Record<string, any>) => {
        return githubRequest("DELETE", `/orgs/${args.org}/copilot/billing/selected_teams`, undefined, undefined);
      },
    },
  • src/index.ts:110-130 (registration)
    Registration in the MCP server: iteration over all tools (including copilotTools) calling server.tool() with name, description, schema, and handler.
    for (const tool of allTools) {
      server.tool(
        tool.name,
        tool.description,
        tool.inputSchema.shape as any,
        async (args: any) => {
          try {
            const result = await tool.handler(args as any);
            return {
              content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
            };
          } catch (err) {
            const message = err instanceof Error ? err.message : String(err);
            return {
              content: [{ type: "text" as const, text: `Error: ${message}` }],
              isError: true,
            };
          }
        }
      );
    }
  • Helper function githubRequest that makes the actual HTTP call to the GitHub API with authentication headers.
    export async function githubRequest<T>(
      method: string,
      path: string,
      body?: Record<string, unknown>,
      params?: Record<string, string | number | boolean | string[] | undefined>
    ): Promise<T> {
      const url = new URL(`${BASE_URL}${path}`);
    
      if (params) {
        for (const [key, value] of Object.entries(params)) {
          if (value === undefined || value === null || value === "") continue;
          if (Array.isArray(value)) {
            url.searchParams.set(key, value.join(","));
          } else {
            url.searchParams.set(key, String(value));
          }
        }
      }
    
      const headers: Record<string, string> = {
        Authorization: `Bearer ${getToken()}`,
        Accept: "application/vnd.github+json",
        "X-GitHub-Api-Version": "2022-11-28",
        "User-Agent": "github-mcp/1.0.0",
      };
    
      if (body) {
        headers["Content-Type"] = "application/json";
      }
    
      const res = await fetch(url.toString(), {
        method,
        headers,
        body: body ? JSON.stringify(body) : undefined,
      });
    
      if (!res.ok) {
        const text = await res.text().catch(() => "");
        let detail = text;
        try {
          const json = JSON.parse(text);
          detail = json.message || text;
          if (json.errors) detail += ` -- ${JSON.stringify(json.errors)}`;
        } catch {}
        throw new Error(`GitHub API error ${res.status}: ${detail}`);
      }
    
      if (res.status === 204) return {} as T;
    
      return res.json() as Promise<T>;
    }
Behavior3/5

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

No annotations provided. The description indicates a destructive action ('Remove') but does not disclose details about the effect (e.g., immediate cancellation, notifications). Basic transparency is achieved, but more context would help.

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 sentence that conveys the essential purpose without any extraneous words. It is optimally concise.

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

Completeness4/5

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

For a simple tool with one parameter and no output schema, the description is largely complete. It could specify that it removes seat assignments for all members of the specified teams, but it is sufficient for context.

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?

The input schema has 100% coverage for the 'org' parameter with a description that matches the tool's context. The description does not add additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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?

The description uses a specific verb 'Remove' and resource 'teams from the Copilot subscription', clearly distinguishing it from sibling tools like 'add_copilot_seats_for_teams' and 'cancel_copilot_seat_assignment_for_users'.

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?

No guidance on when to use this tool versus alternatives (e.g., cancel_copilot_seat_assignment_for_users), nor any prerequisites like required permissions. The description only states the action.

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/Eyalm321/github-mcp'

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