Skip to main content
Glama

github_classroom_get_assignment_grades

Get grades for a GitHub Classroom assignment by providing the assignment ID.

Instructions

Get assignment grades

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assignment_idYesassignment_id

Implementation Reference

  • The handler function for github_classroom_get_assignment_grades that makes a GET request to the GitHub API endpoint /assignments/{assignment_id}/grades.
    handler: async (args: Record<string, any>) => {
      return githubRequest("GET", `/assignments/${args.assignment_id}/grades`, undefined, undefined);
    },
  • Input schema for the tool: requires a single 'assignment_id' string parameter.
    inputSchema: z.object({
      assignment_id: z.string().describe("assignment_id")
    }),
  • The tool is registered as part of the classroomTools array exported from src/tools/classroom.ts (line 5) and imported into the MCP server via src/tools/index.ts (line 9) and src/index.ts (line 12, 63, 110-129).
    export const classroomTools = [
      {
        name: "github_classroom_get_an_assignment",
        description: "Get an assignment",
        inputSchema: z.object({
          assignment_id: z.string().describe("assignment_id")
        }),
        handler: async (args: Record<string, any>) => {
          return githubRequest("GET", `/assignments/${args.assignment_id}`, undefined, undefined);
        },
      },
      {
        name: "github_classroom_list_accepted_assignments_for_an_assignment",
        description: "List accepted assignments for an assignment",
        inputSchema: z.object({
          assignment_id: z.string().describe("assignment_id"),
          page: z.number().optional().describe("The page number of the results to fetch. For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\""),
          per_page: z.number().optional().describe("The number of results per page (max 100). For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\"")
        }),
        handler: async (args: Record<string, any>) => {
          return githubRequest("GET", `/assignments/${args.assignment_id}/accepted_assignments`, undefined, { page: args.page, per_page: args.per_page });
        },
      },
      {
        name: "github_classroom_get_assignment_grades",
        description: "Get assignment grades",
        inputSchema: z.object({
          assignment_id: z.string().describe("assignment_id")
        }),
        handler: async (args: Record<string, any>) => {
          return githubRequest("GET", `/assignments/${args.assignment_id}/grades`, undefined, undefined);
        },
      },
      {
        name: "github_classroom_list_classrooms",
        description: "List classrooms",
        inputSchema: z.object({
          page: z.number().optional().describe("The page number of the results to fetch. For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\""),
          per_page: z.number().optional().describe("The number of results per page (max 100). For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\"")
        }),
        handler: async (args: Record<string, any>) => {
          return githubRequest("GET", `/classrooms`, undefined, { page: args.page, per_page: args.per_page });
        },
      },
      {
        name: "github_classroom_get_a_classroom",
        description: "Get a classroom",
        inputSchema: z.object({
          classroom_id: z.string().describe("classroom_id")
        }),
        handler: async (args: Record<string, any>) => {
          return githubRequest("GET", `/classrooms/${args.classroom_id}`, undefined, undefined);
        },
      },
      {
        name: "github_classroom_list_assignments_for_a_classroom",
        description: "List assignments for a classroom",
        inputSchema: z.object({
          classroom_id: z.string().describe("classroom_id"),
          page: z.number().optional().describe("The page number of the results to fetch. For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\""),
          per_page: z.number().optional().describe("The number of results per page (max 100). For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\"")
        }),
        handler: async (args: Record<string, any>) => {
          return githubRequest("GET", `/classrooms/${args.classroom_id}/assignments`, undefined, { page: args.page, per_page: args.per_page });
        },
      },
    ];
  • 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?

No annotations provided, and the description does not disclose behavioral traits such as whether the operation is read-only, required authentication, rate limits, or what side effects occur. The description is too minimal to inform the agent about behavior.

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 very concise (one sentence). However, it is underspecified and lacks structure. While brevity is valued, this description omits essential details needed for correct tool invocation.

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 no output schema and no annotations, the description fails to explain the output format, possible errors, or any additional context. The tool is simple but still requires more completeness to be useful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one parameter (assignment_id) with a tautological description 'assignment_id'. The tool description does not add any meaning beyond the schema. With 100% schema coverage but zero added value, the parameter semantics are poorly conveyed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get assignment grades' states the verb and resource, but is very terse and does not differentiate from sibling tools like github_classroom_list_accepted_assignments_for_an_assignment, which might also return grade-related data. Lacks clarity on the scope of 'grades'.

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. The description does not specify prerequisites, context, or exclusions. Agents are left to infer usage from the 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