Skip to main content
Glama

Get Codeforces contest rating changes

get_contest_rating_changes
Read-onlyIdempotent

Retrieve the rating deltas applied after a Codeforces contest for each participant, including handle, rank, old and new ratings, and computed change. Available once the contest is rated.

Instructions

Return the rating deltas applied after a rated contest: handle, rank, old rating, new rating and the computed change. Only available once the contest has been rated.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax participants to return (default 50).
contestIdYesNumeric Codeforces contest id, e.g. 1700.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's added value is the gating rule that data exists only for rated contests — real behavioral context an agent needs to avoid a wasted or empty call. It does not discuss error signaling or result ordering, which keeps it below 5.

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 short sentences: the return content first, then the availability constraint. Efficient and front-loaded, though 'rating deltas' and 'the computed change' partially duplicate each other.

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, naming the returned fields is important and is done here; annotations cover safety and the schema covers both parameters. The remaining gap is truncation behavior for the limit parameter, which matters for a tool that can return up to 500 participants.

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%, with contestId and limit (default 50, max 500) fully documented in the schema itself. The description adds nothing about parameter behavior — not what limit truncates relative to, nor ordering — so it sits at the baseline.

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 states a specific verb and resource ('return the rating deltas applied after a rated contest') and enumerates the returned fields (handle, rank, old/new rating, change), which clearly separates it from standings or status tools. It never names a sibling explicitly, so differentiation is inferred rather than stated.

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?

'Only available once the contest has been rated' is a genuine usage precondition that tells the agent when the call will succeed. However, it gives no guidance on when to prefer this over get_user_rating or get_contest_standings, and no exclusions or alternatives are mentioned.

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