Skip to main content
Glama

github_codespaces_delete_from_organization

Delete a specified codespace from an organization by providing org, username, and codespace name.

Instructions

Delete a codespace from the organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgYesorg
usernameYesusername
codespace_nameYescodespace_name

Implementation Reference

  • Definition of the 'github_codespaces_delete_from_organization' tool, including its name, description, input schema, and async handler that performs a DELETE request to /orgs/{org}/members/{username}/codespaces/{codespace_name}
    {
      name: "github_codespaces_delete_from_organization",
      description: "Delete a codespace from the organization",
      inputSchema: z.object({
        org: z.string().describe("org"),
        username: z.string().describe("username"),
        codespace_name: z.string().describe("codespace_name")
      }),
      handler: async (args: Record<string, any>) => {
        return githubRequest("DELETE", `/orgs/${args.org}/members/${args.username}/codespaces/${args.codespace_name}`, undefined, undefined);
      },
    },
  • Input validation schema for github_codespaces_delete_from_organization: requires org (string), username (string), and codespace_name (string)
    inputSchema: z.object({
      org: z.string().describe("org"),
      username: z.string().describe("username"),
      codespace_name: z.string().describe("codespace_name")
    }),
  • src/index.ts:110-129 (registration)
    Generic registration loop that registers all tools (including github_codespaces_delete_from_organization) onto the MCP server using server.tool()
    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,
            };
          }
        }
      );
  • Imports for the codespaces tool file: zod for schema validation and githubRequest from the client helper
    // AUTO-GENERATED by scripts/generate.ts — DO NOT EDIT
    import { z } from "zod";
    import { githubRequest } from "../client.js";
  • The githubRequest helper function that executes HTTP requests against the GitHub API, used by the handler to send the DELETE request
    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>;
    }
Behavior2/5

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

No annotations exist, so the description must carry the behavioral burden. The description only says 'Delete', implying a destructive operation, but provides no details on irreversibility, side effects, or authorization needs. This is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise. However, it lacks structure and could be expanded to include key details without becoming verbose.

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?

For a destructive mutation tool with no annotations or output schema, the description is inadequate. It fails to explain what happens on success/failure, any required permissions, or how the operation affects the organization.

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 covers all three parameters with descriptions, but those descriptions are merely the parameter names (org, username, codespace_name). The description adds no additional context or meaning beyond the schema, so it meets the baseline for high schema coverage.

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 (Delete) and resource (codespace from organization). However, it does not differentiate from sibling tools like github_codespaces_delete_for_authenticated_user or github_codespaces_delete_org_secret, which are easily confused.

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 vs alternatives. It does not mention prerequisites, permissions, or scenarios where this tool should be avoided.

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