Skip to main content
Glama

Yield-Adjusted Component Demand

bpj_yield_adjusted_component_order
Read-onlyIdempotent

Convert finished demand to component requirements and gross up for expected usable yield before rounding to whole pieces.

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": {
      "finished": "<finished>",
      "per": "<per>",
      "yield": "<yield>"
    },
    "name": "bpj_yield_adjusted_component_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
perYes
yieldYes
finishedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world calculation, so safety needs no restatement. The description usefully adds the ordering of operations and the fact that output is rounded to whole pieces. However, the rounding direction (ceiling versus nearest) and the behavior at degenerate inputs such as zero finished units or near-zero yield are not disclosed.

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 sentence with the computation order front-loaded and no filler. Every clause, including the rounding step, carries operational meaning.

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 deterministic three-input calculator with an output schema absent, the definition is adequate but thin. It omits the rounding convention, the treatment of zero-demand input, and any statement about the return type, all of which an agent needs to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the whole burden, and it does tie the three inputs into a formula: finished times per, divided by yield, then rounded. It does not restate that yield is expressed as a percentage or clarify the unit basis of 'per' beyond its bare title, so the compensation is partial rather than complete.

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 a specific transformation chain: convert finished demand into component requirements, gross up for usable yield, then round to whole pieces. That is a concrete verb-plus-resource statement an agent can match to a demand-to-component task. It does not name or rule out any sibling tool, so it falls short of the top mark.

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: an agent infers it should call this when it has finished-unit demand and a yield figure. There is no explicit when-to-use statement and no pointer to alternatives such as an unadjusted component-order or inventory-quantity tool, leaving the agent to guess at boundaries.

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.