codechef-mcp

Get CodeChef profile

get_profile

Read-only

Fetch a CodeChef user's profile by handle as compact structured JSON, including ratings, ranks, solved problems, and contest history, instead of downloading and parsing HTML pages.

Instructions

Fetch a CodeChef user's profile as compact structured JSON: name, star rating, current and highest rating, division, global rank, country rank, problems solved, contests participated, latest contest and recent form. Prefer this over downloading and parsing the profile HTML page.

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

Input Schema

Name	Required	Description	Default
`handle`	Yes	CodeChef username/handle, e.g. 'gennady.korotkevich'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Nov 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the result is compact structured JSON with specific fields, which is useful given there is no output schema, but it does not address failure modes, rate limits, or invalid-handle behavior.

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 tight sentences with zero waste, front-loading the resource and the returned data before the routing guidance. Every clause contributes information.

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 one-parameter read-only tool with full schema coverage, the description is nearly complete and compensates for the absent output schema by listing the returned fields. It could still mention error handling for malformed or unknown handles.

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%, and the single 'handle' parameter is documented in the schema with an example. The description adds no syntax or format detail beyond what the schema already provides, 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?

The description uses a specific verb and resource ('Fetch a CodeChef user's profile') and enumerates the returned fields, so the agent knows exactly what it gets. It does not explicitly differentiate from siblings like get_solved_problems or get_contests, even though several enumerated fields overlap with those tools.

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 by saying to prefer this over downloading and parsing the profile HTML page, which is a meaningful alternative for this data. It stops short of stating when to use a sibling such as get_rating_history or get_contests instead.

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

Deploy Server