Skip to main content
Glama

Get recent Codeforces submissions

get_recent_submissions
Read-onlyIdempotent

Fetch recent Codeforces submissions across the platform, compacted to verdict, problem, language, and runtime, to sample live activity.

Instructions

Return the most recent submissions across the whole Codeforces platform, compacted to verdict, problem, language and runtime. Useful for sampling live activity.

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

Input Schema

NameRequiredDescriptionDefault
countNoHow many to return (default 25).

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 readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the results are 'compacted to verdict, problem, language and runtime', telling the agent the response shape despite there being no output schema. It omits pagination, freshness/recency window and rate-limit behavior, which keeps it short of a 5.

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, with the scope constraint front-loaded before the use case. Every clause carries information an agent can act on.

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 single-parameter read tool with full annotation coverage, the description is nearly sufficient, and the note about which fields are returned compensates for the absent output schema. It could still say more about ordering/freshness of 'most recent' results, which is the one substantive unknown for an agent calling it.

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?

Only one parameter (count) with 100% schema description coverage including default 25 and max 1000, so the schema fully documents it. The description adds nothing about count semantics or the cost of requesting large values, 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 recent submissions) plus a scope qualifier — 'across the whole Codeforces platform' — which distinguishes it from the per-user sibling get_user_submissions without naming it. An agent can tell what it retrieves, though it must infer the contrast with get_user_submissions from the scope phrase rather than an explicit naming.

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?

'Useful for sampling live activity' implies the intended use case (platform-wide activity sampling) but gives no explicit when-not conditions and never names get_user_submissions as the alternative when per-user data is wanted. Usage is implied rather than directed.

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