Skip to main content
Glama

Get Codeforces provider capabilities

get_capabilities
Read-onlyIdempotent

Reports which Codeforces operations are supported, degraded, or unsupported to reveal the server's safe read-only surface area before calling other tools.

Instructions

Report which Codeforces operations this server supports, which are degraded, and which are deliberately unsupported (this adapter is strictly read-only and never submits code or accepts credentials). Call this first to discover the safe surface area.

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": "get_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is supplied structurally. The description adds genuine context on top: it explains that the adapter never submits code and never accepts credentials, which tells the agent why write operations are unavailable rather than merely that they are. It does not describe the shape of the report (e.g., a per-operation status list) despite there being no output schema.

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 sentences, no filler, and the scope statement (supported/degraded/unsupported) is front-loaded before the call-to-action. Every clause carries 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 zero-parameter discovery tool the description covers purpose, constraint and call ordering adequately. The one shortfall is that with no output schema, the description could say what the response actually contains (for example, per-operation status labels or reasons for degradation), which would help the agent interpret results.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is empty and fully self-evident.

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 ('Report') and a specific resource ('which Codeforces operations this server supports'), plus the three buckets reported: supported, degraded, deliberately unsupported. That is far more than a restatement of the name. The only gap versus siblings is that it never contrasts itself with get_health, so an agent must infer that health/uptime differs from capability discovery.

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?

'Call this first to discover the safe surface area' is an explicit, actionable ordering instruction that tells the agent exactly when to reach for this tool. It stops short of a when-not rule or naming an alternative like get_health, so it is clear context without full routing coverage.

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