Skip to main content
Glama

List Codeforces problems by tag and rating

list_problems
Read-onlyIdempotent

Browse Codeforces problems with structured tag and rating filters, returning most-solved matches for all given tags to build targeted practice ladders.

Instructions

Browse the problemset with structured filters instead of a text query. Returns the most-solved problems matching ALL given tags within the rating range. Ideal for building practice ladders.

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": "list_problems"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoTags that must ALL be present, e.g. ['dp','greedy'].
limitNoMax results (default 25).
maxRatingNoMaximum problem rating.
minRatingNoMinimum problem rating.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, which already declare read-only, open-world, idempotent, and non-destructive behavior, the description adds useful behavioral context: results are the most-solved problems and must match ALL given tags within the rating range. It does not detail ordering tie-breaks or output fields.

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 description is three short sentences, front-loaded with purpose and followed by return behavior and a usage example. It contains no repetition or filler.

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?

The annotations and schema already cover safety, idempotency, and full parameter detail, while the description supplies the key selection semantics. With no output schema, a little more detail about returned fields would improve completeness, but the definition is sufficient to invoke the tool correctly.

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 the schema already explains all four parameters. The description reinforces that all tags must match and that ratings form a range, but it adds little meaning beyond the schema's own parameter descriptions.

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: browsing/listing the problemset with structured filters. It distinguishes itself from a text-query approach by saying structured filters instead of a text query, though it does not explicitly name the sibling search_problems tool.

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

Usage Guidelines4/5

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

It gives clear usage context: use structured filters rather than a text query, and it is ideal for building practice ladders. It implies the alternative to text search but does not spell out explicit when-not conditions.

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