Skip to main content
Glama

nephis_fast_batch

Evaluate up to 50 test cases in one HTTP request, running source code concurrently against supplied stdin and expected output for batch coding assessment.

Instructions

50-Testcase Parallel Fast-Batch: Dispatches up to 50 testcases in a single HTTP request to evaluate concurrently in 38ms parallel memory.

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

Input Schema

NameRequiredDescriptionDefault
testsNoList of up to 50 testcases with stdin and expected_output
language_idNoLanguage ID (e.g. 54 for Python, 63 for JavaScript, 71 for Python 3)
source_codeYesSource code to evaluate against tests
submissionsNoAlternative batch submissions format for backward compatibility

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden and does disclose some useful traits: a hard 50-testcase cap, single-request dispatch, and concurrent execution. It omits key behaviors such as what happens if more than 50 are submitted, whether the operation is side-effect free, and what the response contains (no output schema exists).

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 definition is a single front-loaded sentence with no padding around the core idea. The phrase '38ms parallel memory' is somewhat marketing-flavored and less precise than the rest, but overall it is efficient.

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 moderately complex batch-evaluation tool with no annotations and no output schema, the description covers the essential dispatch model and the 50-case limit. It is incomplete on return format, error behavior, and how it differs from the similarly named sibling, leaving meaningful gaps for an agent.

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 the schema already documents each parameter, including that tests is a list of up to 50 with stdin and expected_output. The description adds only the 50-testcase cap on tests, which is useful but minimal, so the baseline 3 is appropriate.

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 states a specific verb and resource: 'Dispatches up to 50 testcases in a single HTTP request to evaluate concurrently.' That is clear enough for an agent to know what the tool does. It does not distinguish itself from the similarly named sibling 'eschaton_fast_batch', so it falls short of a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tools are named. The 'up to 50 testcases' phrasing implies this is for bulk evaluation rather than single-case runs, but that inference is left entirely to the agent.

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