Skip to main content
Glama

Retail Open-to-Buy

bpj_retail_open_to_buy
Read-onlyIdempotent

Calculate open-to-buy at retail by balancing planned sales, markdowns and ending stock against opening stock and orders.

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": {
      "planSales": "<planSales>",
      "markdown": "<markdown>",
      "ending": "<ending>",
      "opening": "<opening>",
      "ordered": "<ordered>"
    },
    "name": "bpj_retail_open_to_buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
endingYes
openingYes
orderedYes
markdownYes
planSalesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 without the description. The description adds real value by revealing the balancing model (sales + markdowns + ending vs. opening + orders), but it never says what the result looks like, whether a negative result means overbought, or how units 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.

Conciseness5/5

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

A single well-formed sentence that front-loads the verb and resource and spends no words on filler. Nothing here could be cut without losing information.

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 purely computational tool with five required numeric inputs, no output schema and no parameter documentation, the description should state what is returned (a retail-currency OTB figure, and its sign convention). That gap is real, though the disclosed formula model and the annotations cover enough that an agent could still call it.

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%, so the description must carry the load; it does partially by naming all five inputs in plain language (planned sales, markdowns, ending stock, opening stock, orders), which maps cleanly onto planSales, markdown, ending, opening and ordered. It does not clarify units, whether inputs are positive magnitudes, or how each enters the arithmetic, leaving the 0% schema gap only half-closed.

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?

States a specific verb ('Calculate') and a specific named retail metric ('open-to-buy at retail'), then enumerates the inputs that make up the calculation. An agent knows exactly what computation this performs; the only missing element is explicit differentiation from the many similarly-prefixed sibling calculators.

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, no prerequisites (e.g. that all figures must be in the same retail currency), and no mention of any alternative calculation. The phrase 'by balancing ... against ...' hints at the model behind it but is not actionable 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.