Skip to main content
Glama

Get Codeforces contest submissions

get_contest_status
Read-onlyIdempotent

Retrieve submissions from a Codeforces contest and optionally filter them by participant handle to review submitted solutions and verdicts.

Instructions

Return submissions made in a specific contest, optionally narrowed to a single handle. Useful for reviewing what a competitor submitted and which verdicts they received.

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

Input Schema

NameRequiredDescriptionDefault
fromNo1-based start index (default 1).
countNoHow many to return (default 25).
handleNoOnly this participant's submissions.
contestIdYesNumeric Codeforces contest id, e.g. 1700.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds that results carry verdict information, which is genuinely useful beyond the annotations, but it says nothing about ordering, result caps, or pagination behavior beyond what the schema implies.

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, no filler, with the core operation front-loaded ahead of the optional narrowing and the use case. Nothing is redundant, though the second sentence is value-framing rather than operational detail.

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 read-only, four-parameter list tool with a fully documented schema and no output schema, the description covers what is returned (submissions with verdicts) and the scope. It is nearly complete; the only gap is the absence of any note on ordering or how to page through large contests, which the from/count parameters hint at but do not explain.

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, handle, from and count all documented in the schema itself. The description's only parameter-adjacent content ('optionally narrowed to a single handle') restates the schema, adding no format or semantic detail, so the baseline of 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 submissions made in a specific contest') plus the optional handle narrowing, so the contest-scoped nature is clear. It does not explicitly distinguish itself from get_user_submissions or get_recent_submissions, leaving the agent to infer the difference from the contestId requirement.

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?

Offers one usage context ('reviewing what a competitor submitted and which verdicts they received'), which implies when to reach for it. However, it names no alternatives and gives no when-not guidance, so an agent comparing it against get_user_submissions or get_recent_submissions gets no routing help.

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