Skip to main content
Glama

Get CodeChef problem details

get_problem
Read-only

Fetches a CodeChef problem's full statement, constraints, time and memory limits, and sample test cases for solving or analyzing it.

Instructions

Fetch full problem statement, constraints, time/memory limits, and sample test cases.

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>",
      "problemCode": "<problemCode>"
    },
    "name": "get_problem"
  }
}

Input Schema

NameRequiredDescriptionDefault
contestCodeYesContest code, e.g. 'START123'
problemCodeYesProblem code, e.g. 'PROB1'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/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 genuine value by disclosing what content comes back (statement, limits, samples), but says nothing about rate limits, authentication, error behavior on invalid codes, or how large the response may be. Useful but not rich beyond the annotations.

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 no filler; every listed item (statement, constraints, limits, samples) corresponds to actual returned content an agent would want to know before calling.

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?

There is no output schema, so the description must carry the return-value burden, and it does so adequately by naming the main sections of the response. For a simple two-required-parameter read tool, the only real omissions are error/precondition behavior and its relationship to list_problems.

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%, with both contestCode and problemCode documented and exemplified in the schema itself. The description adds no parameter-level meaning (no scoping rules, no case sensitivity, no coupling between contest and problem codes), 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?

The description pairs a specific verb ('Fetch') with a specific resource ('problem statement') and enumerates the payload: constraints, time/memory limits, and sample test cases. That is far clearer than a tautology, but it never distinguishes this tool from list_problems, so an agent must infer that this one is for a single problem's details.

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 phrase 'full problem statement' — an agent can reasonably conclude this is for retrieving one problem's detail rather than enumerating problems. There is no explicit statement of when to use this instead of list_problems, no prerequisite (e.g., needing a valid contest/problem code pair), and no note about failures for unknown codes.

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