Skip to main content
Glama

Price and Volume Sales Bridge

bpj_price_volume_sales_bridge
Read-onlyIdempotent

Value the volume change at budget price and the price change at actual volume to reconcile revenue variance.

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": {
      "budgetPrice": "<budgetPrice>",
      "actualPrice": "<actualPrice>",
      "budgetQty": "<budgetQty>",
      "actualQty": "<actualQty>"
    },
    "name": "bpj_price_volume_sales_bridge"
  }
}

Input Schema

NameRequiredDescriptionDefault
actualQtyYes
budgetQtyYes
actualPriceYes
budgetPriceYes

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description needn't repeat it. The description does add genuinely useful method context — the valuation convention (volume at budget price, price at actual volume) that defines a standard bridge. It stops short of saying what the tool returns or how the decomposition is presented, which matters since there is no output schema.

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 that front-loads the computation method and ends with the business purpose. No filler, no restatement of the tool name, and nothing redundant with the annotations or schema.

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?

With four required numeric inputs, no output schema, and no annotations about return shape, an agent still lacks the most decision-relevant detail: what the response contains (volume effect, price effect, total variance) and in what units. The description covers the computation logic adequately but leaves the result side underspecified for a pure-calculation tool.

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%, but the schema still carries titles ('Budget unit price', 'Actual units', etc.) and numeric bounds, so basic meaning is present. The description reinforces the mapping by naming budget price, actual volume, and the two effects, but it does not clarify sign conventions, currency/unit assumptions, or whether quantities are integers, so it only partially compensates for the coverage gap.

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 computation (a price/volume sales bridge) and states its purpose: reconciling revenue variance by valuing volume change at budget price and price change at actual volume. That is far more specific than a tautology. It does not, however, differentiate itself from adjacent siblings such as bpj_purchase_price_variance or bpj_units_volume_flow, so an agent must infer which variance tool to pick.

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 phrase 'to reconcile revenue variance' — the agent can guess this is the tool for decomposing a revenue gap into price and volume effects. There is no explicit when-to-use, no when-not-to-use, and no named alternative among the many variance/volume siblings. No prerequisites (e.g., both budget and actual figures required) are 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.