Skip to main content
Glama

github_codespaces_get_repo_secret

Get a specific repository secret for GitHub Codespaces by providing owner, repo, and secret name.

Instructions

Get a repository secret

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesowner
repoYesrepo
secret_nameYessecret_name

Implementation Reference

  • The handler function that executes the 'github_codespaces_get_repo_secret' tool logic - makes a GET request to GitHub's API to fetch a repository secret.
    handler: async (args: Record<string, any>) => {
      return githubRequest("GET", `/repos/${args.owner}/${args.repo}/codespaces/secrets/${args.secret_name}`, undefined, undefined);
    },
  • Input schema defining the required parameters: owner (string), repo (string), and secret_name (string).
    inputSchema: z.object({
      owner: z.string().describe("owner"),
      repo: z.string().describe("repo"),
      secret_name: z.string().describe("secret_name")
    }),
  • src/index.ts:110-130 (registration)
    Tool registration in the MCP server - tools are registered via server.tool() using their 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,
            };
          }
        }
      );
    }
  • Tool definition object containing name, description, inputSchema, and handler - part of the codespacesTools array.
    {
      name: "github_codespaces_get_repo_secret",
      description: "Get a repository secret",
      inputSchema: z.object({
        owner: z.string().describe("owner"),
        repo: z.string().describe("repo"),
        secret_name: z.string().describe("secret_name")
      }),
      handler: async (args: Record<string, any>) => {
        return githubRequest("GET", `/repos/${args.owner}/${args.repo}/codespaces/secrets/${args.secret_name}`, undefined, undefined);
      },
    },
  • The githubRequest helper function used by the handler to make authenticated HTTP requests 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?

With no annotations provided, the description carries the full burden of disclosure. It fails to mention any behavioral traits such as idempotency, permissions required, or potential errors (e.g., secret not found). The description is purely functional without operational context.

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 brief (1 sentence) and front-loaded with the core purpose. It is appropriately concise, though it could include more detail without sacrificing clarity.

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?

The description lacks important context: it does not explain what the tool returns (e.g., secret details, but not the value), the scope of the secret (Codespaces-specific), or any required permissions. Given the absence of an output schema, the description should compensate but does not.

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 descriptions for all 3 parameters, but they are tautological (e.g., owner/owner). Per instructions, since schema description coverage is 100%, baseline is 3. The description adds no further meaning to the parameters, so score remains 3.

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 'Get a repository secret' clearly indicates the action (get) and the resource (a repository secret within Codespaces). It distinguishes itself from sibling tools like create_or_update, delete, or list by specifying the retrieval operation.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like list_repo_secrets or create_or_update_repo_secret, nor does it mention any prerequisites or context.

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