Skip to main content
Glama

Get Codeforces provider health

get_health
Read-onlyIdempotent

Probe the official Codeforces API to report transport, schema, auth, and upstream health, last error, and request latency, helping diagnose failing tool calls.

Instructions

Probe the official Codeforces API and report transport, schema, auth and upstream health, plus the last observed error and request latency. Use this to diagnose failing tool calls.

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

Input Schema

NameRequiredDescriptionDefault
probeNoPerform a live upstream probe (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real context beyond that: it performs a live upstream probe and surfaces last observed error plus request latency, which tells the agent this is a network-dependent diagnostic. It stops short of noting whether the live probe consumes rate limit or may be slow.

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: the first front-loads what is probed and what is reported, the second gives the use case. No redundant or decorative wording.

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?

With no output schema, the description compensates by enumerating the health dimensions and diagnostic fields (transport, schema, auth, upstream, last error, latency), which is enough to interpret results. It does not indicate the shape of a failure response or whether errors are raised versus reported, a minor remaining gap for a diagnostic tool.

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 coverage is 100% and the single `probe` parameter is fully documented in the schema, including its default of true. The description does not restate or enrich that toggle (e.g., when to set probe=false for a cheap cached check), 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?

States a specific verb ('probe') and a precisely scoped resource (the official Codeforces API's transport, schema, auth and upstream health), plus the diagnostic payload it returns. It is inherently distinct from the data-retrieval siblings, though it never explicitly contrasts itself with them.

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?

'Use this to diagnose failing tool calls' gives a clear triggering condition, which is the main thing an agent needs. It does not state when not to use it (e.g., don't call it pre-emptively before every request) or name alternatives for verification.

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