Skip to main content
Glama

get_upcoming_contests

Fetches upcoming LeetCode contest schedules, including titles, start times, durations, and registration links, so you can plan participation in Weekly or Biweekly contests.

Instructions

Retrieves the schedule of upcoming LeetCode contests (read-only, no auth). Returns titles, slugs, start times (epoch & ISO), durations, and direct registration links as JSON. Use this to check upcoming Weekly or Biweekly contests.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_upcoming_contests"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does so well: it declares the operation read-only and auth-free, and discloses the shape of the response (titles, slugs, epoch/ISO times, durations, registration links). It does not mention rate limits or pagination, though a finite upcoming-contest list makes those largely moot.

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?

Three short sentences, each doing distinct work: purpose, behavioral/return disclosure, and usage context. The most decision-relevant information (what it returns) is front-loaded with zero filler.

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

Completeness5/5

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

No output schema exists, and the description compensates by enumerating the returned fields, so an agent knows what it will receive. For a parameterless read tool, nothing further is needed to call it correctly.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. No misleading parameter hints are present.

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?

States a specific verb and resource ('Retrieves the schedule of upcoming LeetCode contests') and scopes the content precisely, making it clearly distinct from siblings like get_user_contest_ranking or get_daily_challenge without needing to open either schema.

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

Usage Guidelines4/5

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

'Use this to check upcoming Weekly or Biweekly contests' gives a clear usage context and implicitly rules out user-specific or historical contest queries. It stops short of naming an explicit alternative or a when-not-to-use condition, but the sibling set offers no close substitute.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.