Skip to main content
Glama

Operating Leverage Scenario

bpj_operating_leverage_scenario
Read-onlyIdempotent

Hold price, unit variable cost and fixed costs constant to model profit after a volume change.

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": {
      "sales": "<sales>",
      "variable": "<variable>",
      "fixed": "<fixed>",
      "change": "<change>"
    },
    "name": "bpj_operating_leverage_scenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixedYes
salesYes
changeYes
variableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 a closed-world model, so safety behavior needs no restating. The description does add real behavioral context by declaring the ceteris paribus assumptions of the model, but it never states what the tool returns (e.g. a projected profit figure) or how the inputs are interpreted.

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 well-formed sentence with no filler, and the modeling assumption is front-loaded. It is efficient, though brevity here comes at the cost of the missing usage and return-value information.

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?

For a four-parameter required-input calculator with no output schema and zero schema description coverage, the definition is thin. It omits what the computation returns, the units/percentage convention for the change parameter, and any guidance on interpreting results, leaving the agent to infer all of that.

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%, so the description must carry parameter meaning, and it partly does by naming the four held-constant drivers. However it introduces a mismatch: it says 'price' and 'unit variable cost', while the schema defines 'sales' as Revenue and 'variable' as Total variable costs, and it does not clarify that 'change' is a percentage. That misalignment could lead an agent to pass wrong-magnitude values.

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 specific analytical operation: modeling profit after a volume change while holding price, unit variable cost and fixed costs constant. That is enough to distinguish it from sibling scenario tools such as bpj_constant_elasticity_price_scenario, though the naming of the alternative is left implicit.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. The only usage signal is the implied constraint that assumptions must be held constant, which the agent must infer applies to a static-scenario analysis.

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.