Skip to main content
Glama

Group uncovered line numbers

bpj_release_coverage_misses
Read-onlyIdempotent

Combine consecutive zero-hit lines from a numbered coverage map into ranges.

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": {
      "hits": "<hits>"
    },
    "name": "bpj_release_coverage_misses"
  }
}

Input Schema

NameRequiredDescriptionDefault
hitsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered externally. The description adds nothing beyond restating the operation: it does not disclose the expected input encoding, the shape of the returned ranges, ordering, or how non-zero lines are treated, all of which matter for a transform tool with no output schema.

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. Its brevity works structurally, though the same brevity is the source of the specification gaps scored elsewhere.

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 no output schema and no parameter documentation, the description is the only source of behavioral information, and it omits both the input encoding and the output range format. For a data-transformation tool that is the entire job of the description, so the definition is materially incomplete.

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 single parameter 'hits' has 0% schema description coverage, and the description does not compensate by explaining the string format (separators, line-number/count pairing, how zero is represented) or what the 6000-character limit implies. 'Numbered coverage map' is the only hint and is too vague for an agent to construct 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?

States a specific verb ('combine') and resource ('consecutive zero-hit lines from a numbered coverage map into ranges'), which is distinct from siblings like bpj_release_weighted_coverage or bpj_compare_line_sets. The only weakness is that 'numbered coverage map' is left as an undefined concept, so the agent knows the transformation but not exactly what it operates on.

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 statement of when to use this tool, when not to, or which sibling to prefer for adjacent tasks (e.g., weighted coverage or line-set comparison). The agent must infer usage purely from the verb, with no contextual triggers or exclusions.

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.