Skip to main content
Glama

eschaton_special_judge

Validates competitive programming solutions using custom checker code to handle float tolerances, multiple valid answers, and graph permutations inside isolated sandboxes.

Instructions

Custom competitive programming checker binary validator: evaluates solutions with custom tolerances (e.g. 1e-6 float precision), multiple valid outputs, or graph permutations.

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": {
      "source_code": "<source_code>",
      "checker_code": "<checker_code>"
    },
    "name": "eschaton_special_judge"
  }
}

Input Schema

NameRequiredDescriptionDefault
stdinNoTestcase stdin5.0
language_idNoSolution language ID
source_codeYesSolution source code
checker_codeYesCustom validator checker source code
expected_outputNoTestcase reference answer2.5
checker_language_idNoChecker language ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does not say whether source_code and checker_code are compiled and executed in a sandbox, what limits apply, what verdict or error form is returned, or what happens when the checker itself fails to compile — all essential for a tool that runs untrusted code.

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?

It is a single front-loaded sentence with no filler, and the most useful differentiators (tolerances, multiple valid outputs, permutations) come first. The awkward 'checker binary validator' compound costs it a point on clarity.

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

Completeness2/5

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

With six parameters, two required, no annotations, and no output schema, the definition should explain the execution model and the shape of the verdict. Instead it stops at the feature list, leaving an agent unable to predict return values or failure modes before invoking it.

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%, so all six parameters are already documented in the input schema, establishing a baseline of 3. The description adds nothing about how expected_output interacts with checker_code, what stdin defaults mean, or how language_id values are chosen.

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 (evaluates) and resource (solutions judged by a custom checker), and the enumerated cases (float tolerances, multiple valid outputs, graph permutations) make the tool's identity concrete. However, the opening phrase 'checker binary validator' is garbled and could be misread as validating a binary rather than running a checker, and it never distinguishes itself from siblings like eschaton_execute_suite or eschaton_fast_batch.

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?

It gives clear selection conditions: use this when judging requires custom tolerances, multiple acceptable answers, or permutation-equivalent outputs. That implicitly rules out standard exact-match judging, but no sibling is named and there is no explicit when-not guidance.

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

Deploy Server

Other Tools