Skip to main content
Glama

Get Codeforces contest standings

get_contest_standings
Read-onlyIdempotent

Fetch a Codeforces contest standings table with metadata, problems, and ranked rows, or filter results by specific handles to check competitor results.

Instructions

Fetch the standings table for a contest: contest metadata, the problem list, and a bounded window of ranked rows with points, penalty, hacks and per-problem results. Pass 'handles' to look up specific competitors instead of the top of the table.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contestId": "<contestId>"
    },
    "name": "get_contest_standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNo1-based rank to start from (default 1).
countNoHow many rows to return (default 20).
handlesNoOnly these handles' rows.
contestIdYesNumeric Codeforces contest id, e.g. 1700.
showUnofficialNoKeep non-CONTESTANT rows if present (default false). Note: anonymous Codeforces access only serves the official table, so unofficial/virtual rows are normally absent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, open-world, and non-destructive behavior, so the description need not repeat safety hints. The description adds useful context about the bounded row window and the returned sections, but it does not discuss rate limits, authentication requirements, or pagination behavior beyond the 'bounded window' phrase.

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?

The definition is two dense, well-structured sentences with zero filler. The core purpose is front-loaded, and the second sentence delivers the key parameter-driven distinction without restating the schema.

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?

With no output schema present, the description does a solid job naming what the returned data contains: contest metadata, problem list, and ranked rows with points, penalty, hacks, and per-problem results. It is nearly complete for a read-only retrieval tool, though it could mention auth or rate-limit constraints for fully anonymous Codeforces access.

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 coverage is 100%, so all five parameters are already documented in the input schema. The description adds a little meaning by framing 'handles' as an alternative to the default top-of-table view, but it does not add syntax or format details beyond what the schema already states.

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?

The description opens with a specific verb and resource ('Fetch the standings table for a contest') and then enumerates exactly what is returned: contest metadata, problem list, and ranked rows with points, penalty, hacks, and per-problem results. That level of detail distinguishes it from siblings like get_contest_status or get_contest_rating_changes.

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

Usage Guidelines3/5

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

The only usage guidance is 'Pass handles to look up specific competitors instead of the top of the table,' which clarifies one parameter-driven mode. It does not explain when to prefer this tool over sibling contest tools, nor does it state any exclusions or prerequisites.

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