Skip to main content
Glama

Get Codeforces rating history

get_user_rating
Read-onlyIdempotent

Retrieve a Codeforces user's contest rating history with per-contest deltas, ranks, tier labels, best rating, and biggest gain or drop to analyze rating trends.

Instructions

Return a user's full contest rating history (newest first) with per-contest rating deltas, ranks, tier labels, best rating, biggest gain and biggest drop. Use for trend questions.

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": {
      "handle": "<handle>"
    },
    "name": "get_user_rating"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRecent contests to return (default 50).
handleYesCodeforces handle, e.g. 'tourist' or 'Benq'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/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 structurally. The description adds ordering ("newest first") and the aggregation fields that come back, which is genuine added context, but it says nothing about invalid-handle failure behavior or how pagination interacts with the history. There is no output schema, so the return-shape burden sits mostly on this one sentence.

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?

A single dense sentence with the return contents front-loaded and the usage hint trailing. Nothing is wasted, though the enumeration of return fields makes it read as a compressed list rather than a structured statement.

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

Completeness3/5

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

For a no-output-schema tool the description does a reasonable job of naming what comes back. However, calling it the "full" history while the schema defaults limit to 50 is a mild tension the definition never reconciles, and nothing is said about behavior for an unknown handle. These gaps keep it at minimum viable rather than complete.

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%: handle and limit are both documented in-schema, including the default of 50 and the 1-500 bounds. The description adds no syntax or format meaning beyond that, so 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?

The description names a specific verb and resource ("Return a user's full contest rating history") and enumerates the returned contents: deltas, ranks, tier labels, best rating, biggest gain and biggest drop. That is far more specific than a sibling like get_user_stats. It never names an alternative tool, so it lands at clear-but-undifferentiated rather than fully distinguishing.

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?

"Use for trend questions" gives one implied context for selection, but there are no exclusions and no explicit routing away from plausible overlaps such as get_contest_rating_changes or get_user_stats. An agent can guess when to reach for it, but the definition does not tell it when not to.

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