Skip to main content
Glama

Order fail-fast tests

bpj_release_fail_fast_order
Read-onlyIdempotent

Rank independent tests by failure probability per second and estimate time with stop-on-first-failure.

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": {
      "tests": "<tests>"
    },
    "name": "bpj_release_fail_fast_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
testsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.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 closed-world, so the safety profile is covered. The description adds real behavioral content beyond that: it explains the ranking criterion and that the time estimate assumes stop-on-first-failure. It says nothing about ordering direction, tie-breaking, or what the result looks like.

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?

A single front-loaded sentence with no wasted words; the core operation and model are stated immediately. It is arguably too terse for a tool whose only input lacks format documentation, but as prose it is efficiently structured.

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?

There is no output schema and no annotation-level detail on returns, so the description should carry the input contract, yet the freeform 'tests' string format is never specified. For a tool whose entire correctness depends on how that one string is encoded, the definition leaves the most important question unanswered.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter 'tests', which is an unconstrained-format string capped at 6000 characters with only the title 'Test probabilities and runtimes'. The description hints at the expected content (probabilities and runtimes per test) but gives no format — JSON, CSV, or otherwise — so an agent cannot reliably construct a valid call without guessing.

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 ('Rank independent tests') and names the ranking metric (failure probability per second) plus the scheduling model (stop-on-first-failure), so the tool's purpose is identifiable. It does not explicitly distinguish itself from the many sibling bpj_release_* tools, but the operation is clear enough to select without opening the schema.

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, when-not-to-use, or named alternative guidance. The word 'independent' implies a precondition (tests must not depend on each other), but this is left implicit rather than stated as a requirement, and there is no indication of how this differs from bpj_release_test_shards or bpj_release_test_history.

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.