Skip to main content
Glama

github_code_scanning_get_sarif

Retrieve information about a SARIF upload for code scanning in a GitHub repository. Provide owner, repo, and SARIF ID to get the upload details.

Instructions

Get information about a SARIF upload

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesowner
repoYesrepo
sarif_idYessarif_id

Implementation Reference

  • The handler function for github_code_scanning_get_sarif. Makes a GET request to the GitHub API endpoint /repos/{owner}/{repo}/code-scanning/sarifs/{sarif_id} to retrieve information about a SARIF upload.
    handler: async (args: Record<string, any>) => {
      return githubRequest("GET", `/repos/${args.owner}/${args.repo}/code-scanning/sarifs/${args.sarif_id}`, undefined, undefined);
    },
  • Zod input schema defining the required parameters: owner, repo, and sarif_id (all strings).
    inputSchema: z.object({
      owner: z.string().describe("owner"),
      repo: z.string().describe("repo"),
      sarif_id: z.string().describe("sarif_id")
    }),
  • The tool definition object registered in the codeScanningTools array, containing name, description, inputSchema, and handler.
    {
      name: "github_code_scanning_get_sarif",
      description: "Get information about a SARIF upload",
      inputSchema: z.object({
        owner: z.string().describe("owner"),
        repo: z.string().describe("repo"),
        sarif_id: z.string().describe("sarif_id")
      }),
      handler: async (args: Record<string, any>) => {
        return githubRequest("GET", `/repos/${args.owner}/${args.repo}/code-scanning/sarifs/${args.sarif_id}`, undefined, undefined);
      },
    },
  • src/index.ts:64-64 (registration)
    Registration of the code-scanning module (which contains github_code_scanning_get_sarif) in the MCP server's allToolModules array.
    { category: "code-scanning", tools: codeScanningTools },
  • The githubRequest helper function that performs authenticated HTTP requests to the GitHub API. Used by the handler to make the actual GET request.
    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 should disclose behavioral traits. It does not mention that this is a read operation, nor what happens if the sarif_id is invalid or if the upload is not found.

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?

Single sentence, no redundant words. Efficient but could be expanded slightly without harming conciseness.

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?

No output schema, and the description does not explain what is returned. For a simple tool, the lack of return value description leaves the agent uncertain.

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 minimal descriptions (just the parameter names). The tool description adds no extra meaning beyond what the schema already provides, meeting the baseline.

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 clearly states the action 'Get information' and the resource 'SARIF upload', which distinguishes it from sibling tools like 'upload_sarif' and 'get_alert'. However, it does not specify what kind of information is returned.

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 'get_analysis' or 'get_alert'. The description lacks context about prerequisites or scenarios.

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