Skip to main content
Glama

List Codeforces contests

get_contest_list
Read-onlyIdempotent

Lists Codeforces contests with start time, duration, type, and phase, letting you filter by upcoming, running, or finished status or switch to the gym archive.

Instructions

List Codeforces contests with start time, duration, type and phase. Filter by phase (BEFORE = upcoming, CODING = running, FINISHED = past) or switch to the gym archive.

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_contest_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
gymNoList gym contests instead of regular ones (default false).
limitNoMax contests to return (default 25).
phaseNoOnly contests in this phase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety and side-effect behavior are covered without the description. The description adds the returned field set and the semantic meaning of the phase values, which is genuine value, but says nothing about pagination behavior, default result ordering, or upstream rate limits.

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

Conciseness4/5

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

Two tight sentences with no filler; the returned-field list is front-loaded and the filtering instruction follows. The trailing 'or switch to the gym archive' is compact and earns its place.

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 zero-required-parameter read-only list tool with a fully documented schema and rich annotations, the description covers purpose, filtering, and the gym variant adequately. No output schema exists, yet the description compensates by enumerating the returned fields.

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%, so the baseline is 3; each parameter is already documented in the schema including defaults and the limit bounds. The description only adds plain-language glosses for three of the five phase enum members, leaving PENDING_SYSTEM_TEST and SYSTEM_TEST undefined, and does not mention the limit parameter at all.

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?

The description gives a specific verb and resource ('List Codeforces contests') and names the fields returned (start time, duration, type, phase), so the agent knows exactly what data comes back. It does not, however, distinguish itself from the sibling get_upcoming_contests, which overlaps with its phase=BEFORE mode.

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?

Usage is clearly framed: filter by phase with the enum members glossed in plain language (BEFORE = upcoming, CODING = running, FINISHED = past), or switch to the gym archive via gym. There are no explicit exclusions or named alternatives, so the agent must infer when to prefer get_upcoming_contests over this tool.

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