Skip to main content
Glama

Purchase Price Variance

bpj_purchase_price_variance
Read-onlyIdempotent

Apply the difference between actual and standard prices to actual purchasing volume; a positive variance represents extra cost.

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": {
      "actualQty": "<actualQty>",
      "standard": "<standard>",
      "discount": "<discount>"
    },
    "name": "bpj_purchase_price_variance"
  }
}

Input Schema

NameRequiredDescriptionDefault
discountYes
standardYes
actualQtyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 covered. The description adds one genuinely useful behavioral fact beyond them: the sign convention, where a positive result means extra cost. It says nothing about rounding, unit consistency, or what the returned value looks like.

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 compact sentence with the core operation front-loaded and no filler. It could have used the remaining room to map the parameters rather than staying this 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 three-parameter arithmetic tool with no output schema, the definition conveys the formula shape and the meaning of the result's sign, which is the essential minimum. It falls short on rounding behavior, units/currency assumptions, and the identity of the 'discount' input.

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% and the only parameter information comes from titles, so the description needed to compensate. It mentions 'actual and standard prices' and 'actual purchasing volume', loosely mapping to standard and actualQty, but it never explains the 'discount' parameter, whose title ('Alternative purchase unit price') actually denotes the actual price — the single most confusing input is left unaddressed.

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 states a concrete computational purpose: applying the gap between actual and standard prices to actual purchasing volume, i.e. a price-variance calculation. This clearly separates it from siblings such as bpj_overhead_absorption_variance or bpj_pairs_weighted_variance, though it never explicitly contrasts itself with them.

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 guidance, no preconditions (e.g. prices must be in the same currency/unit of measure), and no routing to alternative variance tools. An agent must infer the use case purely from the formula language.

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.