Skip to main content
Glama

get-contest-details

Retrieve contest information from LeetCode using the contest URL slug to access details about programming competitions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contestSlugYesThe URL slug of the contest

Implementation Reference

  • Primary registration of the 'get-contest-details' tool, including input schema (contestSlug: string) and inline handler that fetches data from LeetCodeService and returns formatted JSON response or error.
    server.tool(
      "get-contest-details",
      {
        contestSlug: z.string().describe("The URL slug of the contest")
      },
      async ({ contestSlug }) => {
        try {
          const data = await leetcodeService.fetchContestDetails(contestSlug);
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify(data, null, 2)
            }]
          };
        } catch (error: unknown) {
          const errorMessage = error instanceof Error ? error.message : String(error);
          return {
            content: [{ type: "text", text: `Error: ${errorMessage}` }],
            isError: true
          };
        }
      }
    );
  • src/index.ts:24-24 (registration)
    Top-level registration call that invokes registerContestTools to add the get-contest-details tool (among others) to the MCP server.
    registerContestTools(server, leetcodeService);
  • Supporting service method in LeetCodeService that executes the GraphQL query to fetch contest details by slug.
    async fetchContestDetails(contestSlug: string) {
      return this.executeQuery(contestDetailsQuery, { contestSlug });
    }
  • GraphQL query definition used to fetch detailed contest information including title, description, timing, and participating questions.
    export const contestDetailsQuery = `
      query contestData($contestSlug: String!) {
        contest(titleSlug: $contestSlug) {
          title
          titleSlug
          description
          startTime
          duration
          originStartTime
          isVirtual
          questions {
            questionId
            title
            titleSlug
            difficulty
          }
        }
      }
    `;
  • Inline handler function within the tool registration that processes the input, calls the service, and structures the MCP-compatible response.
    async ({ contestSlug }) => {
      try {
        const data = await leetcodeService.fetchContestDetails(contestSlug);
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify(data, null, 2)
          }]
        };
      } catch (error: unknown) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return {
          content: [{ type: "text", text: `Error: ${errorMessage}` }],
          isError: true
        };
      }
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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?

Tool has no description.

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?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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?

Tool has no description.

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/doggybee/mcp-server-leetcode'

If you have feedback or need assistance with the MCP directory API, please join our Discord server