Skip to main content
Glama

github_code_security_get_single_configuration_for_enterprise

Retrieve a specific code security configuration for an enterprise to manage and enforce code security policies.

Instructions

Retrieve a code security configuration of an enterprise

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enterpriseYesenterprise
configuration_idYesconfiguration_id

Implementation Reference

  • The handler for github_code_security_get_single_configuration_for_enterprise. It calls githubRequest with GET method to the endpoint /enterprises/{enterprise}/code-security/configurations/{configuration_id}.
    handler: async (args: Record<string, any>) => {
      return githubRequest("GET", `/enterprises/${args.enterprise}/code-security/configurations/${args.configuration_id}`, undefined, undefined);
    },
  • Input schema defining the two required parameters: enterprise and configuration_id, both strings.
    inputSchema: z.object({
      enterprise: z.string().describe("enterprise"),
      configuration_id: z.string().describe("configuration_id")
    }),
  • src/index.ts:65-65 (registration)
    Registration of the codeSecurityTools array (which contains this tool) into the MCP server.
    { category: "code-security", tools: codeSecurityTools },
  • src/index.ts:110-129 (registration)
    Loop that registers all tools (including this one) with 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,
            };
          }
        }
      );
  • The githubRequest helper function used by the handler to make the actual HTTP call 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 provided; description carries full burden for behavioral disclosure. Only states 'Retrieve', which is a read operation, but lacks details about authentication requirements, rate limits, or any side effects.

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

Conciseness5/5

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

Single sentence with no wasted words. Appropriately concise for a straightforward retrieval operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists; description does not explain return values or structure. Behavioral context is minimal. Adequate for a simple tool but could be improved by mentioning what is returned.

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?

Schema coverage is 100% with both parameters documented (enterprise, configuration_id). The description adds no additional meaning beyond the schema. Score at baseline as per rubric.

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 the verb 'Retrieve', the resource 'a code security configuration', and scope 'of an enterprise'. It distinguishes from sibling tools like 'github_code_security_get_configurations_for_enterprise' (list) and 'github_code_security_get_configuration' (likely for org).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. The purpose is implied by the name (single configuration vs list), but the description does not mention exclusions or alternative tools.

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