Skip to main content
Glama

Get Codeforces user submissions

get_user_submissions
Read-onlyIdempotent

Fetch a Codeforces user's recent submissions and trim them to verdict, problem, language, runtime and memory to keep LLM context concise.

Instructions

Return a user's recent submissions, compacted to verdict, problem, language, runtime and memory. Raw Codeforces submission objects are very large; this trims them for LLM context.

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

Input Schema

NameRequiredDescriptionDefault
fromNo1-based index of the first submission (default 1).
countNoHow many to return (default 25).
handleYesCodeforces handle, e.g. 'tourist' or 'Benq'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 covered. The description adds real value by disclosing the compaction behavior and the reason for it (raw objects are very large), but says nothing about ordering (newest first?), pagination limits, or failure modes for an invalid handle.

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, both earning their place: the first declares the return shape, the second justifies the trimming decision. Front-loaded with the outcome rather than background. Minor redundancy between 'recent submissions' in sentence one and the raw-object rationale in sentence two.

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 usefully enumerates the returned fields, which is the key missing piece an agent would otherwise have to guess. For a simple read-only list tool with fully documented parameters and full annotation coverage, the remaining gaps (ordering, error behavior) are small.

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 from, count and handle each documented including defaults and bounds, so the baseline is 3. The description adds nothing beyond the schema about these parameters and slightly muddies them by calling the results 'recent' while the schema exposes arbitrary offset pagination.

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 a user's recent submissions') and adds the projected fields (verdict, problem, language, runtime, memory), so the agent knows exactly what comes back. It stops short of distinguishing itself from the near-identically named sibling get_recent_submissions, which is the one place an agent could hesitate.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. With a sibling called get_recent_submissions in the catalog, an agent has no textual basis to pick between them; usage is only inferable from the handle/from/count parameters.

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