Skip to main content
Glama

Combine test coverage counts

bpj_release_weighted_coverage
Read-onlyIdempotent

Pool per-module hit and total counts before computing one weighted coverage fraction.

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": {
      "modules": "<modules>"
    },
    "name": "bpj_release_weighted_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
modulesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description need not repeat safety claims. It adds that the tool pools counts rather than enumerating modules, but it does not disclose input format expectations, validation behavior, or output shape, leaving meaningful behavioral gaps.

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?

A single front-loaded sentence with no filler; the operation and result are stated immediately. It is appropriately sized for a one-parameter computation tool.

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 is simple, but with 0% schema description coverage, no output schema, and a free-form string parameter, the agent needs more than a one-sentence description to call it correctly—especially the expected module-count encoding and what exactly is returned. The description leaves those operational details unresolved.

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?

The sole parameter is documented only as a string titled 'Module coverage counts' with no schema description. The description clarifies that it contains per-module hit and total counts, but it does not specify the string encoding or format (JSON, CSV, delimiter syntax, etc.), which is essential for constructing a valid value.

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 concrete operation (pooling hit and total counts) and the resulting metric (one weighted coverage fraction), so the agent can tell this is an aggregation/coverage calculation rather than a history or shard inspection. It does not name a sibling alternative to use instead, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'before computing one weighted coverage fraction' implies a preprocessing use case, but it does not state when to choose this tool over sibling coverage tools or when not to use it. Guidance is implied rather than explicit.

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.