Skip to main content
Glama

Get Codeforces leaderboard

get_rated_users
Read-onlyIdempotent

Fetch high-rated Codeforces users, optionally filtered by minimum rating or recent activity, with capped results to protect context size.

Instructions

Return the top rated Codeforces users, optionally only currently-active users or above a minimum rating. The upstream list has hundreds of thousands of entries, so results are always capped to protect context size.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax users to return (default 100).
minRatingNoOnly users at or above this rating.
activeOnlyNoOnly users active in the last month (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior, so the bar is lower. The description adds a genuinely useful behavioral fact the annotations do not carry: the upstream list is enormous and results are always capped to protect context size, which explains why limits exist and why the output is truncated.

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?

Two sentences, zero filler; the core behavior comes first and the cap rationale follows. Everything said 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 three-param, no-required-param list tool with no output schema, the description covers purpose, filtering and the result cap. It leaves sort order and result shape unstated, but the cap warning addresses the main risk an agent faces when calling an open-world list endpoint.

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 limit, minRating and activeOnly are already fully documented including defaults and bounds. The description restates the filter concepts but adds no semantics (e.g., sort order, tie-breaking) beyond the schema, 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?

States a specific verb and resource ('Return the top rated Codeforces users') plus the optional filters. It does not name a sibling such as get_user_rating or compare_users to distinguish itself, so it falls short of a 5, but the purpose is unambiguous.

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?

Usage is only implied through the mention of optional active-only and minimum-rating filters; there is no explicit statement of when to choose this over per-user tools like get_user_rating. The agent must infer the routing itself.

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