Skip to main content
Glama

github_codespaces_get_org_secret

Retrieve a specific secret from a GitHub organization's codespace secrets store by providing the organization name and secret name.

Instructions

Get an organization secret

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgYesorg
secret_nameYessecret_name

Implementation Reference

  • Handler for github_codespaces_get_org_secret tool. Makes a GET request to /orgs/{org}/codespaces/secrets/{secret_name}.
    {
      name: "github_codespaces_get_org_secret",
      description: "Get an organization secret",
      inputSchema: z.object({
        org: z.string().describe("org"),
        secret_name: z.string().describe("secret_name")
      }),
      handler: async (args: Record<string, any>) => {
        return githubRequest("GET", `/orgs/${args.org}/codespaces/secrets/${args.secret_name}`, undefined, undefined);
      },
  • Input schema for github_codespaces_get_org_secret. Expects 'org' (string) and 'secret_name' (string) parameters.
    {
      name: "github_codespaces_get_org_secret",
      description: "Get an organization secret",
      inputSchema: z.object({
        org: z.string().describe("org"),
        secret_name: z.string().describe("secret_name")
      }),
  • src/index.ts:55-67 (registration)
    The tool is registered as part of 'codespaces' category via codespacesTools array. The server registers all tools from this array using server.tool() in the for loop at lines 110-129.
    const allToolModules = [
      { category: "actions", tools: actionsTools },
      { category: "activity", tools: activityTools },
      { category: "agent-tasks", tools: agentTasksTools },
      { category: "apps", tools: appsTools },
      { category: "billing", tools: billingTools },
      { category: "campaigns", tools: campaignsTools },
      { category: "checks", tools: checksTools },
      { category: "classroom", tools: classroomTools },
      { category: "code-scanning", tools: codeScanningTools },
      { category: "code-security", tools: codeSecurityTools },
      { category: "codes-of-conduct", tools: codesOfConductTools },
      { category: "codespaces", tools: codespacesTools },
  • The githubRequest helper function that executes the actual HTTP request to the GitHub API. The handler for this tool calls githubRequest with method 'GET'.
    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 provided, so description should disclose read-only nature and any permissions. Only says 'Get', which implies read, but lacks details on whether secret value is returned or if authentication is required.

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

Conciseness2/5

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

Extremely terse (5 words), but lacks substance. Conciseness is not favored when it sacrifices completeness; every word should provide value.

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 simple structure and no output schema, description should at least hint at return format or error cases. It does not, leaving significant gaps.

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?

High schema coverage (100%) but parameter descriptions are minimal (just 'org' and 'secret_name'). Description adds no extra meaning beyond the schema, but baseline is 3.

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?

Description clearly states 'Get an organization secret', which is a specific verb+resource. It differentiates from siblings like list_org_secrets and get_repo_secret by focusing on org-level secret retrieval.

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 like list_org_secrets or get_repo_secret. Does not specify that this retrieves a single secret by name.

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