Skip to main content
Glama

Constant Elasticity Price Scenario

bpj_constant_elasticity_price_scenario
Read-onlyIdempotent

Model new demand with a supplied constant-elasticity power curve and compare contribution at a fixed unit 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": {
      "price": "<price>",
      "newPrice": "<newPrice>",
      "oldQty": "<oldQty>",
      "elasticity": "<elasticity>",
      "cost": "<cost>"
    },
    "name": "bpj_constant_elasticity_price_scenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYes
priceYes
oldQtyYes
newPriceYes
elasticityYes

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, non-destructive and closed-world, so the safety profile is covered. The description adds the real value: it discloses that the computation applies a power curve to derive new demand and then compares contribution at a fixed unit cost. It omits other behavioral context, such as what result shape comes back and what assumptions the contribution comparison makes.

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 front-loaded sentence with no filler and no repetition. It is dense but earns its words, though it could be tightened by naming the two outputs (new quantity, contribution delta).

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?

This is a five-parameter quantitative tool with no output schema and no schema documentation, and the description is one sentence. An agent has no way to know the underlying formula, whether costs are per-unit or total, or what the response contains. That leaves significant gaps for a computation whose correctness depends on model assumptions.

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 does not. It hints that elasticity and unit cost drive the model, but never explains the roles of price, newPrice, or oldQty, nor the functional form linking them. An agent cannot tell from the text whether oldQty is a baseline or a cap.

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 concrete verb+resource: model new demand via a constant-elasticity power curve and compare contribution at a fixed unit cost. That is specific enough to distinguish a pricing scenario calculation from generic arithmetic siblings. It falls short of 5 only because it doesn't contrast itself with close relatives like the price-volume sales bridge.

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 statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The phrase 'supplied constant-elasticity power curve' implies elasticity must come from the caller, but that is inference rather than guidance.

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.