Skip to main content
Glama

Rolled First-Pass Yield

bpj_rolled_first_pass_yield
Read-onlyIdempotent

Multiply conditional first-pass yields across three sequential stages to estimate output passing all stages without rework.

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": {
      "total": "<total>",
      "a": "<a>",
      "b": "<b>",
      "d": "<d>"
    },
    "name": "bpj_rolled_first_pass_yield"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes
bYes
dYes
totalYes

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the meaningful modeling assumption (independent conditional yields, three stages, no rework), which is real context beyond the annotations. It still omits what the response looks like and whether the result is a percentage or a unit count.

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 verb and the three-stage scope come first. Nothing in the sentence is redundant or padding.

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, four required parameters, and 0% schema description coverage, the description is too thin. An agent cannot tell that yields are percentages bounded 0-100, how 'total' enters the calculation, or whether the return is a percentage, a unit count, or both.

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% (only short titles exist), so the description should carry parameter meaning, and it does not name a, b, d, or total. Critically, 'total' (units produced) is never mentioned, leaving its role in the computation — input to a unit-count result versus a validation bound — unstated.

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 specific verb and resource: 'Multiply conditional first-pass yields across three sequential stages'. It even accounts for the no-rework assumption and the output notion ('passing all stages'), so the computation is unambiguous. It does not differentiate from siblings, though none of the listed siblings appear to overlap closely.

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?

Usage is only implied by the purpose statement: an agent can infer this is for rolling sequential stage yields into a single throughput figure. There is no explicit when-to-use vs. when-not, no mention of prerequisites such as yields being conditional/independent, and no alternatives named.

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.