Skip to main content
Glama

Analyze Codeforces user performance

get_user_stats
Read-onlyIdempotent

Analyze a Codeforces user's submissions to compute solved vs attempted, acceptance rate, verdicts, top languages, strongest tags, rating distribution, and hardest solved problem in one call.

Instructions

Compute derived analytics from a user's submission history: unique problems solved vs attempted, acceptance rate, verdict breakdown, favourite languages, strongest tags, solved-by-rating distribution and hardest solved problem. Answers 'how good is X' in one call.

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

Input Schema

NameRequiredDescriptionDefault
handleYesCodeforces handle, e.g. 'tourist' or 'Benq'.
sampleSizeNoHow many recent submissions to analyze (default 2000).

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 establish readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds real value beyond them by revealing that the analysis is computed over a bounded sample of recent submissions rather than full history, which changes how results should be interpreted.

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 sentences, front-loaded with the core purpose and followed by the metric enumeration that doubles as a result contract. The metric list is dense but each item is informative; no filler wording.

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, the description carries the burden of describing returns and does so by naming each derived metric produced, which is sufficient for an agent to judge fitness. Missing only secondary details like whether zero-solve users or errors are reflected in the output.

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% with documented bounds and defaults for both handle and sampleSize, so the schema does the heavy lifting. The description's phrase 'submission history' loosely ties to sampleSize but adds no format or trade-off detail (e.g. what a larger sample costs).

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 opens with a specific verb+resource ('Compute derived analytics from a user's submission history') and enumerates the exact metrics produced, which clearly separates it from raw-data siblings like get_user_submissions or get_user_rating. It stops short of naming a sibling to route away from, but an agent can infer the derived-vs-raw boundary.

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?

'Answers "how good is X" in one call' implies the use case (summary judgment about a user) rather than stating it as guidance. There is no explicit when-not or alternative named, so the agent must infer that raw submission listings should go elsewhere.

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