Skip to main content
Glama

Balance test shards by runtime

bpj_release_test_shards
Read-onlyIdempotent

Assign longest historical test runtimes first to the currently least-loaded shard.

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

Input Schema

NameRequiredDescriptionDefault
testsYes
shardsYes

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 openWorldHint=false, so the safety and determinism profile is covered structurally. The description contributes genuine behavioral content by disclosing the greedy longest-first heuristic the tool applies, which the annotations cannot convey. It omits, however, what the result looks like and how ties or uneven splits are handled.

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 filler or redundancy, and the algorithmic rule leads. Its brevity borders on under-specification for a tool with an undocumented required JSON parameter, but there is no wasted wording to trim.

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?

The tool takes a required JSON blob at 0% schema coverage and returns no output schema, so the description must explain both the input encoding and the return shape; it explains neither. An agent knows the balancing policy but not what to pass as JSON or what assignment it will get back.

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%, so the description carries the burden for both parameters, and it only partially does so. 'Historical test runtimes' hints at the tests parameter but never reveals that it is a bounded JSON string (maxLength 6000) or what shape that JSON takes, and 'least-loaded shard' only indirectly implies the shard count, without noting the 1–30 range.

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 and policy: 'Assign longest historical test runtimes first to the currently least-loaded shard,' which identifies both the input material (historical runtimes) and the target resource (shards). It never states what the tool actually produces (a shard assignment mapping) and never distinguishes itself from siblings such as bpj_release_fail_fast_order or bpj_release_test_history, so it stops 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 when-to-use or when-not-to-use guidance, no prerequisite information, and no named alternative. The sentence describes an algorithm rather than a calling context, so an agent must infer that this is the sharding tool to reach for over the other test-related siblings.

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.