Codeforces

Contest List

contest_list

Read-onlyIdempotent

All contests. Pass gym=true for gym contests.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`gym`	No

Output Schema

TableJSON Schema

Name	Required	Description
`result`	No	Array of contest objects
`status`	Yes	Response status (OK or FAILED)
`comment`	No	Error comment (if status is FAILED)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "gym": false
+  },
+  {
+    "gym": true
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "comment": {
+      "description": "Error comment (if status is FAILED)",
+      "type": "string"
+    },
+    "result": {
+      "description": "Array of contest objects",
+      "items": {
+        "properties": {
+          "city": {
+            "description": "City name",
+            "type": "string"
+          },
+          "country": {
+            "description": "Country code",
+            "type": "string"
+          },
+          "description": {
+            "description": "Contest description",
+            "type": "string"
+          },
+          "difficulty": {
+            "description": "Difficulty level",
+            "type": "number"
+          },
+          "durationSeconds": {
+            "description": "Contest duration in seconds",
+            "type": "number"
+          },
+          "frozen": {
+            "description": "Is scoreboard frozen",
+            "type": "boolean"
+          },
+          "icpcPhase": {
+            "description": "ICPC contest phase",
+            "type": "string"
+          },
+          "id": {
+            "description": "Contest ID",
+            "type": "number"
+          },
+          "kind": {
+            "description": "Contest kind",
+            "type": "string"
+          },
+          "name": {
+            "description": "Contest name",
+            "type": "string"
+          },
+          "phase": {
+            "description": "Contest phase (BEFORE, CODING, PENDING_SYSTEM_TEST, SYSTEM_TEST, FINISHED)",
+            "type": "string"
+          },
+          "preparedBy": {
+            "description": "Prepared by (handle)",
+            "type": "string"
+          },
+          "relativeTimeSeconds": {
+            "description": "Seconds since contest start (if started)",
+            "type": "number"
+          },
+          "season": {
+            "description": "Season name",
+            "type": "string"
+          },
+          "startTimeSeconds": {
+            "description": "Unix timestamp of contest start",
+            "type": "number"
+          },
+          "type": {
+            "description": "Contest type (CF, IOI, ICPC)",
+            "type": "string"
+          },
+          "websiteUrl": {
+            "description": "Contest website URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "Response status (OK or FAILED)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds the 'gym' parameter but lacks details on pagination, result format, or other behaviors. Adequate but not enhanced.

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?

The description is very short and front-loaded. It is concise, but could benefit from minimal structure. No wasted words.

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

Completeness2/5

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

Despite having rich annotations and an output schema, the description lacks context about what contests are, the output format, or how to interpret results. Insufficient for an agent to fully decide.

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 0%, so the description compensates partially by explaining 'Pass gym=true for gym contests.' However, it does not elaborate on the meaning of 'gym contests' or the default behavior.

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 'All contests' is vague and does not specify the verb or action (e.g., list, retrieve) nor the exact resource (contest list). It fails to distinguish from sibling tools like 'contest_standings'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It only mentions the 'gym' parameter but does not provide context for usage or exclusions.

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

All Codeforces tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.