Skip to main content
Glama

github_apps_scope_token

Generate a scoped access token for a GitHub App by providing the client ID and optional request body.

Instructions

Create a scoped access token

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_idYesclient_id
bodyNoRequest body (JSON object)

Implementation Reference

  • The handler for github_apps_scope_token. It makes a POST request to /applications/{client_id}/token/scoped with an optional body.
    handler: async (args: Record<string, any>) => {
      return githubRequest("POST", `/applications/${args.client_id}/token/scoped`, args.body, undefined);
    },
  • Input schema for github_apps_scope_token: requires client_id (string) and optional body (JSON object).
    inputSchema: z.object({
      client_id: z.string().describe("client_id"),
      body: z.record(z.string(), z.unknown()).optional().describe("Request body (JSON object)")
    }),
  • The tool definition/registration within the appsTools array in src/tools/apps.ts.
    {
      name: "github_apps_scope_token",
      description: "Create a scoped access token",
      inputSchema: z.object({
        client_id: z.string().describe("client_id"),
        body: z.record(z.string(), z.unknown()).optional().describe("Request body (JSON object)")
      }),
      handler: async (args: Record<string, any>) => {
        return githubRequest("POST", `/applications/${args.client_id}/token/scoped`, args.body, undefined);
      },
    },
  • src/index.ts:110-120 (registration)
    Registration of all tools (including github_apps_scope_token) with the MCP server via 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) }],
            };
  • The githubRequest helper function used by the handler to make the actual HTTP request to the GitHub 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?

No annotations exist, and the description does not disclose behavioral traits such as authentication requirements, rate limits, or the specific meaning of 'scoped'. The agent is left without critical context for safe invocation.

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 concise (one sentence), which saves space but sacrifices informativeness. While it is not verbose, it could afford an additional sentence to clarify scope and usage without becoming overly lengthy.

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 absence of annotations and output schema, and the minimal schema descriptions, the description fails to provide enough context for an agent to understand the tool's scope, purpose differentiation, or expected behavior. Important details are missing, such as what the body parameter should contain or how the token will be scoped.

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 provides basic descriptions for both parameters (client_id and body), achieving 100% coverage. However, the description adds no additional meaning beyond what the schema already states, so it meets the baseline expectation but does not compensate for lack of parameter usage context.

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 'Create a scoped access token' clearly states the action and resource, but fails to differentiate from similar tools like github_apps_create_installation_access_token or github_apps_reset_token, leaving ambiguity about what 'scoped' implies.

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 provided on when to use this tool versus alternatives. The description lacks any context about prerequisites, preferred use cases, or situations where other token tools would be more appropriate.

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