Skip to main content
Glama

Preview a test matrix

bpj_preview_test_matrix
Read-onlyIdempotent

Calculate the number of combinations across test dimensions and preview the first 16 jobs.

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": {
      "dimensions": "<dimensions>"
    },
    "name": "bpj_preview_test_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
dimensionsYes

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, idempotentHint, non-destructive and closed-world, so the safety profile needs no restating. The description adds one genuinely useful behavioral fact beyond the annotations: the output is truncated to the first 16 jobs, which tells the agent the preview is a sample rather than the full matrix. It does not say what happens with very large matrices or whether the count is exact.

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; both the computation and the preview cap are stated immediately. It is efficient, though the terse phrasing leaves the reason for the 16-job cap unstated.

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 one-parameter pure-compute tool with no output schema, the description is nearly adequate on the output side but fails on the input side: an agent must guess the JSON structure of the required `dimensions` argument, which is the only thing it can get wrong. There is also no note on whether the returned count is capped or what output format to expect.

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?

There is one parameter, and schema description coverage is 0% — only a title ("JSON object mapping dimensions to option arrays") and a 4500-char limit exist. The description's phrase "across test dimensions" hints that the input is dimensional but gives no example shape such as {"browser": ["chrome","firefox"]}, no minimum/maximum dimension counts, and no serialization guidance. With zero coverage from the schema, the description should carry this burden and does not.

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 two specific verbs and their resources: "Calculate the number of combinations across test dimensions" and "preview the first 16 jobs." An agent knows exactly what the tool returns (a combination count plus a sample of jobs) and can distinguish it from sibling compute-style tools. It stops short of naming a contrasting sibling, so it is not 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?

No when-to-use or when-not-to-use guidance is given. The word "preview" weakly implies a non-committal exploration step, but the description never says whether this is a pre-flight check before a real execution tool or a standalone estimator. No alternatives or exclusions are mentioned.

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.