Skip to main content
Glama

Make or Buy Crossover

bpj_make_buy_crossover
Read-onlyIdempotent

Find the minimum whole-unit volume at which internal production covers its extra fixed cost, and compare at annual demand.

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": {
      "setup": "<setup>",
      "makeCost": "<makeCost>",
      "standard": "<standard>",
      "annual": "<annual>"
    },
    "name": "bpj_make_buy_crossover"
  }
}

Input Schema

NameRequiredDescriptionDefault
setupYes
annualYes
makeCostYes
standardYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the agent knows this is a safe, pure computation. The description adds nothing beyond that: it does not say how rounding of the whole-unit volume is handled, what the returned comparison looks like, or how ties are resolved. With annotations covering the safety profile, a 3 is appropriate.

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?

One dense sentence with no boilerplate, and the core operation (minimum volume) is front-loaded before the annual-demand comparison. Nothing is wasted, though the compression leaves the mechanics slightly terse.

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 four-parameter deterministic calculator with no output schema, the description conveys the concept of the computation but not the shape of the answer or which figure is the headline result. An agent could call it correctly, but would be guessing at what comes back and how the annual-demand comparison is expressed.

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 must carry the parameter burden. It adds real meaning for two of four inputs, clarifying that setup is the extra fixed cost specific to making and that the comparison is performed over annual demand, and it implies that makeCost and standard are the competing unit costs. It never explicitly explains the relationship between makeCost and standard (the per-unit variable cost versus the purchase price), which is the crux of the calculation.

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?

States a specific verb and result: finding the minimum whole-unit volume where internal production offsets its extra fixed cost, then comparing at annual demand. This is clearly a make-versus-buy break-even calculation rather than a generic cost tool. It does not, however, distinguish itself from conceptually similar siblings such as bpj_agency_hire_crossover or bpj_lease_buy_present_cost.

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?

No explicit when-to-use, when-not-to-use, or alternative-naming guidance is given. The calculation described makes the intended context (deciding between in-house production and purchasing) obvious by implication, but the agent must infer it rather than being told.

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.