Skip to main content
Glama

github_classroom_get_an_assignment

Retrieve details of a specific assignment in GitHub Classroom by providing its ID.

Instructions

Get an assignment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assignment_idYesassignment_id

Implementation Reference

  • The handler function that executes the 'github_classroom_get_an_assignment' tool. It makes a GET request to /assignments/{assignment_id} using the githubRequest client.
    handler: async (args: Record<string, any>) => {
      return githubRequest("GET", `/assignments/${args.assignment_id}`, undefined, undefined);
    },
  • Input schema for the tool, defined using Zod. Accepts a single required string parameter 'assignment_id'.
    inputSchema: z.object({
      assignment_id: z.string().describe("assignment_id")
    }),
  • The tool is defined as part of the 'classroomTools' array in src/tools/classroom.ts, with name 'github_classroom_get_an_assignment' and description 'Get an assignment'.
    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);
        },
      },
  • src/index.ts:110-130 (registration)
    Tools are registered with the MCP server in src/index.ts via server.tool() calls, iterating over all tool objects from combined tool modules.
    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 that performs the actual HTTP request to the GitHub API, used by the tool handler.
    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>;
    }
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden for behavioral disclosure. It fails to mention that it returns a single assignment object, requires authentication, or any side effects. The minimal text provides no behavioral context.

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?

The description is extremely concise but at the expense of useful information. While short, it lacks front-loaded context and every word does not earn its place due to vagueness.

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

Completeness1/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 should compensate with richer details. It fails to explain what the assignment object contains or how the ID relates to other resources, leaving the agent underinformed.

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

Parameters1/5

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

Although schema description coverage is 100%, the parameter description is simply 'assignment_id', which adds no meaning beyond the schema. The description does not clarify the format or expected values of the identifier.

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

Purpose2/5

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

The description 'Get an assignment' states a verb and resource but is essentially a tautology of the tool name. It does not specify that the assignment is from GitHub Classroom nor differentiate it from sibling tools like 'github_classroom_get_assignment_grades' or 'github_classroom_get_a_classroom'.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, scope (e.g., classroom, org), or typical use cases.

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