Skip to main content
Glama

Expiry Sell-Through Pace

bpj_expiry_sell_through_pace
Read-onlyIdempotent

Find the daily sales pace needed to clear stock by expiry and project unsold units at the existing pace.

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": {
      "stock": "<stock>",
      "expiry": "<expiry>",
      "daily": "<daily>"
    },
    "name": "bpj_expiry_sell_through_pace"
  }
}

Input Schema

NameRequiredDescriptionDefault
dailyYes
stockYes
expiryYes

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 this a read-only, idempotent, closed-world computation, so the safety profile is covered. The description adds that the tool does two things—derive a required pace and project unsold units—but says nothing about the demand-constancy assumption, behavior when daily demand is 0 (stock never clears), or how the two results relate.

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 efficient sentence that front-loads the core computation before the projection clause; nothing is redundant. It is concise but under-informative rather than padded.

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?

With no output schema and no annotations covering return semantics, the description should say what the result looks like (pace in units/day? unsold unit count? which horizon?). It also omits the modeling assumption that average daily demand stays flat, which materially affects interpretation of the projection.

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 carries the burden, and it only partly does. It implies stock and expiry, but the word 'daily' in the description reads as the output pace rather than the input, which is average daily demand in units—an ambiguity the schema titles alone must resolve. No units, ranges, or format guidance are added.

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 gives two specific verbs and their resources: 'find the daily sales pace needed to clear stock by expiry' and 'project unsold units at the existing pace.' That is enough to distinguish it from the surrounding calculators, though it never names a sibling or states the contrast.

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 when-to-use guidance, no statement of prerequisites (e.g., that demand is assumed constant), and no exclusions or alternatives among the many sibling tools. The agent must infer applicability from the one-line purpose alone.

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.