Skip to main content
Glama

Get Codeforces user profile

get_user_info
Read-onlyIdempotent

Fetch structured Codeforces profile data for 1–10 handles, including rating, max rating, rank/tier, country, organization, contribution, and registration date.

Instructions

Fetch structured profile data for 1-10 Codeforces handles: rating, max rating, rank/tier, country, organization, contribution and registration date.

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": {
      "handles": "<handles>"
    },
    "name": "get_user_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
handlesYesOne to ten Codeforces handles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds the field-level return contents and the batch cap, but says nothing about behavior for invalid or unregistered handles, rate limiting, or partial failures in a multi-handle request.

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?

A single front-loaded sentence with the verb, the scope constraint and the returned fields, with no filler or repetition.

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 simple read-only lookup with no output schema, enumerating the returned fields in the description is exactly the right compensating detail, and the annotations carry the safety profile. Minor gaps remain around error handling for unknown handles, which matters for a batch-capable endpoint.

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?

With a single parameter at 100% schema description coverage, the schema already specifies the array shape, 1-10 bounds and the 3-24 character handle format. The description echoes the 1-10 batch limit but adds no new meaning about handle semantics, so 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?

The description gives a specific verb ('Fetch'), a concrete resource ('structured profile data') and enumerates the payload fields (rating, max rating, rank/tier, country, organization, contribution, registration date), so an agent knows exactly what comes back. It does not, however, contrast itself with closely named siblings like get_user_rating or get_user_stats, which overlap on rating data.

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?

Usage is only implied by the content of the returned fields; there is no explicit statement of when to prefer this tool over get_user_rating, get_user_stats or compare_users. The one operational constraint it does give, the 1-10 handle batch size, is useful but is a parameter bound rather than routing guidance.

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