Skip to main content
Glama

github_codespaces_stop_for_authenticated_user

Stop a running GitHub Codespace for the authenticated user by specifying its name.

Instructions

Stop a codespace for the authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codespace_nameYescodespace_name

Implementation Reference

  • The handler function that executes the tool logic: sends a POST request to /user/codespaces/{codespace_name}/stop to stop a codespace for the authenticated user.
    handler: async (args: Record<string, any>) => {
      return githubRequest("POST", `/user/codespaces/${args.codespace_name}/stop`, undefined, undefined);
    },
  • Input schema using Zod, validating a single required string parameter 'codespace_name'.
    inputSchema: z.object({
      codespace_name: z.string().describe("codespace_name")
    }),
  • The tool is defined as one entry in the exported 'codespacesTools' array, registered in src/index.ts where it is iterated and registered via server.tool().
      {
        name: "github_codespaces_stop_for_authenticated_user",
        description: "Stop a codespace for the authenticated user",
        inputSchema: z.object({
          codespace_name: z.string().describe("codespace_name")
        }),
        handler: async (args: Record<string, any>) => {
          return githubRequest("POST", `/user/codespaces/${args.codespace_name}/stop`, undefined, undefined);
        },
      },
    ];
  • The githubRequest helper function used by the handler to make authenticated HTTP requests to the GitHub REST API.
    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?

With no annotations, the description carries full burden for behavioral disclosure. It only says 'stop' without explaining effects (e.g., state preservation, billing, recoverability). Critical traits for a stop operation are omitted.

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

Conciseness3/5

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

The description is extremely short (4 words), which is concise but under-specified. It lacks necessary detail, so conciseness comes at the expense of completeness.

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 lack of annotations and output schema, the description is insufficient. It does not cover side effects, return values, or usage context, leaving the agent underinformed about a simple but potentially impactful operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one parameter with a description that merely repeats its name. The tool description adds no explanation of what the parameter represents or how to use it, failing to add value beyond the schema.

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

Purpose3/5

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

The description states the verb 'Stop' and resource 'codespace', clearly indicating the action. However, it provides no additional context to distinguish from sibling tools like stop_in_organization or start_for_authenticated_user, making it merely a restatement of the name.

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 is given on when to use this tool versus alternatives (e.g., github_codespaces_stop_in_organization). The description does not mention scope, prerequisites, or when not to use it.

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