Skip to main content
Glama

Get upcoming Codeforces contests

get_upcoming_contests
Read-onlyIdempotent

Returns the next scheduled Codeforces contests in chronological order, including hours until each starts, so you can answer 'when is the next contest' questions.

Instructions

Return the next scheduled Codeforces contests, soonest first, including how many hours away each one starts. Use for 'when is the next contest' questions.

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
limitNoMax contests to return (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds behavior annotations don't: result ordering (soonest first) and a derived 'hours away' value, which matters because there is no output schema. It stops short of covering empty-result behavior or the per-contest fields returned.

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?

Two sentences, zero waste, with the core capability and ordering front-loaded before the usage cue. Nothing is redundant with the title.

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

Completeness4/5

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

For a simple one-parameter read tool with no output schema, the description supplies the essentials: what is returned, ordering, and one derived field. Minor gaps remain around the shape of each contest entry and behavior when no contests are scheduled.

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 description coverage is 100%, and the single 'limit' parameter is fully documented in the schema with default and bounds. The description never mentions the limit or its interaction with result ordering, so it adds no meaning beyond the schema — the baseline 3 applies.

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?

States a specific verb and resource ('Return the next scheduled Codeforces contests') plus ordering ('soonest first') and an added computed field ('how many hours away'). The word 'next' implies a forward-looking subset, which implicitly separates it from get_contest_list, but no sibling is named explicitly.

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?

Gives a concrete triggering intent: "Use for 'when is the next contest' questions." That is clear usage context, though it offers no exclusions or pointer to get_contest_list for historical/full listings.

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