Skip to main content
Glama

List CodeChef contest problems

list_problems
Read-only

Retrieve all problems in a CodeChef contest by contest code, including problem codes, names, and submission counts for contest analysis.

Instructions

List all problems in a CodeChef contest with codes, names, and submission counts.

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": {
      "contestCode": "<contestCode>"
    },
    "name": "list_problems"
  }
}

Input Schema

NameRequiredDescriptionDefault
contestCodeYesContest code, e.g. 'START123'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/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 safety and external-reach semantics are covered. The description usefully discloses the return fields (codes, names, submission counts), which matters because there is no output schema, but it says nothing about ordering, limits, or partial results.

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?

One front-loaded sentence with no filler, and the scope plus returned fields come first. It is efficiently sized for a simple read tool, though it stops before any routing detail that would fully justify the top band.

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 listing tool with full schema coverage and no output schema, the description supplies the result fields an agent would otherwise lack. Nothing critical is missing, though ordering or volume behavior for large contests is unaddressed.

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 contestCode parameter already carries a format example ('START123'). The description adds no meaning beyond the schema, so the baseline 3 for fully documented parameters 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 names a specific verb and resource ('List all problems in a CodeChef contest') and adds the returned fields ('codes, names, and submission counts'), which distinguishes it from the singular get_problem sibling. It stops short of explicitly naming a sibling it is not, so it lands just below the top band.

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: the agent can infer this is the bulk listing for a given contest, as opposed to get_problem or get_solved_problems. There is no explicit when-to-use statement, no exclusion against related listing tools, and no prerequisite or scope note beyond the required contest code.

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