Skip to main content
Glama

Markdown Volume Hurdle

bpj_markdown_volume_hurdle
Read-onlyIdempotent

Find whole units needed at the reduced price to preserve original total contribution and recover incremental campaign 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>",
      "cost": "<cost>",
      "oldQty": "<oldQty>",
      "fixed": "<fixed>"
    },
    "name": "bpj_markdown_volume_hurdle"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYes
fixedYes
priceYes
oldQtyYes
newPriceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/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 without description help. Beyond that, the description gives only the economic objective: it does not state how the result is rounded (implicitly upward, since 'whole units'), what happens when newPrice is below cost or when no feasible volume exists, or whether a single count or a breakdown is returned, and there is no output schema to compensate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single, front-loaded sentence with no filler, which is good. But brevity here comes at the cost of under-specification rather than efficiency; the sentence is dense with undefined jargon that a second clause could have unpacked.

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 five-parameter financial calculation with no output schema and no parameter documentation, the description does far too little: it is missing the formula, rounding rule, failure/edge cases, and return shape. An agent could plausibly call it correctly but could not predict or sanity-check the result.

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% for all five required parameters, so the description carries the full burden. It never explains the role of each input in the computation — e.g. how 'fixed' campaign cost is amortized, or how oldQty and price define the original contribution baseline — leaving only the terse schema titles ('Merchandise unit cost', 'Fixed campaign execution cost', etc.) as guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb and object — finding the whole unit count at a reduced price that preserves original contribution and recovers the incremental campaign cost — so the computation goal is inferable. However, key domain terms ('contribution', 'hurdle', 'markdown' as a price cut rather than a text format, especially given the many bpj_markdown_* document siblings) are left undefined, and there is no differentiation from the pricing siblings bpj_price_volume_sales_bridge and bpj_units_volume_flow.

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 the pricing/volume siblings, no prerequisite or input-validity guidance, and no indication of when the result is not meaningful. The agent must guess at the use case from a single sentence.

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.