Skip to main content
Glama

AutoTasker Hub — China Social Data API

codeforces_contests

Codeforces contest list with phase, start time, duration, ICPC/CF type. $0.01 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "codeforces_contests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
upcomingOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the $0.01 USDC cost and output fields, but omits read-only status, authentication needs, rate limits, pagination behavior, and the default upcomingOnly behavior.

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?

The description is brief and front-loads the core resource and returned fields. The pricing note is relevant and placed last, though the wording is terse and fragmentary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter list tool, the description covers the resource, output fields, and cost. However, with no annotations and no output schema, it should say more about default filtering, pagination, and parameter behavior to fully support correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not mention either the limit or upcomingOnly parameter. The listed fields are output data, not parameter semantics, so the description does nothing to compensate for the undocumented input schema.

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 clearly identifies the resource as a Codeforces contest list and names the included fields: phase, start time, duration, and ICPC/CF type. It does not explicitly differentiate from sibling tools, but no sibling appears to be a contest-listing alternative.

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?

The definition gives no when-to-use guidance, no alternatives, and no explanation of when upcoming-only filtering applies. It only states what data the tool returns.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.