Skip to main content
Glama

Check binary release matrix coverage

bpj_release_artifact_matrix
Read-onlyIdempotent

Find missing binaries against the Cartesian product of requested operating systems and architectures.

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": {
      "platforms": "<platforms>",
      "arches": "<arches>",
      "built": "<built>"
    },
    "name": "bpj_release_artifact_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
builtYes
archesYes
platformsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 scope, so the safety profile is covered. The description adds genuine context by explaining that the check is against a Cartesian product of OS/architecture combinations, but it says nothing about result shape, how 'built' entries are matched, or normalization expectations. With annotations carrying safety, a moderate score is warranted.

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 terseness is efficient, though the brevity leaves the gaps noted in other dimensions rather than being a structural flaw.

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?

For a three-required-parameter tool with no schema descriptions and no output schema, the definition is under-specified. An agent would not know how to format the 'built' list versus the 'platforms'/'arches' lists, or what the returned missing set looks like.

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% and there are three required parameters, so the description must carry the burden. It only indirectly maps to two of them (platforms, arches); 'built' is never mentioned, and the encoding of all three free-form strings (delimiters, casing, maxLength 6000) is left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Find missing binaries') and a resource (binaries), and the phrase 'Cartesian product of requested operating systems and architectures' explains the comparison basis. However, it never accounts for the third required input 'built', which is essential to what 'missing' means, and it does not distinguish itself from close siblings such as bpj_release_coverage_misses.

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 coverage checks. An agent must infer usage purely from the one-line purpose and the tool name.

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.