Skip to main content
Glama

Summarize test outcome history

bpj_release_test_history
Read-onlyIdempotent

Count passes, failures and state transitions in an ordered sequence of test outcomes.

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": {
      "history": "<history>"
    },
    "name": "bpj_release_test_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
historyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 profile is fully covered without the description. The description adds that the computation is over an ordered sequence and that state transitions are tracked, but it does not say how a transition is defined or what the result contains.

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?

One sentence, front-loaded with the verb and the counted quantities, with no filler or repetition. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, annotated, pure-computation tool this is nearly sufficient, but with no output schema the description should indicate the returned shape (counts of each category plus transition count) and define what counts as a state transition. Without that, an agent cannot predict the response format.

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 must carry the meaning of the single parameter. It only restates that history is an ordered sequence of outcomes; the encoding constraint ("P or F") and the 2000-character cap live solely in the schema, and the description never clarifies how outcomes must be formatted or whether separators are allowed.

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 gives a concrete verb ("count") and the exact quantities counted (passes, failures, state transitions) over a specified input (an ordered sequence of test outcomes). It is clear what the tool does, but it never differentiates itself from adjacent siblings such as bpj_release_test_shards or bpj_audit_test_traceability, so an agent cannot route between them from this text alone.

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 prerequisites, and no named alternative. The only hint is the required input shape, from which usage is inferred rather than stated.

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.