Skip to main content
Glama

Free Shipping Contribution Floor

bpj_free_shipping_contribution_floor
Read-onlyIdempotent

Find the merchandise subtotal required to fund shipping while retaining a target order contribution.

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": {
      "shippingCost": "<shippingCost>",
      "retained": "<retained>",
      "contribution": "<contribution>"
    },
    "name": "bpj_free_shipping_contribution_floor"
  }
}

Input Schema

NameRequiredDescriptionDefault
retainedYes
contributionYes
shippingCostYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered without description help. The description adds the modeling intent but discloses nothing about the underlying relationship among the inputs, units, or what happens at boundary inputs (e.g. contribution at 0.01%). Nothing contradicts the annotations.

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?

One sentence, front-loaded with the verb and the outcome, with no filler or redundant restatement of the title. Every word maps to an input or the result.

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, three undocumented parameters, and 0% schema description coverage, the definition should explain the returned quantity and its units or edge behavior. A single sentence leaves the agent to guess the formula and the return shape for a pure computation tool.

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 burden. It gestures at all three inputs ('shipping', 'target order contribution', 'contribution') and clarifies that the output is a subtotal, but it never states that retained is an absolute currency amount while contribution is a percentage margin, nor explains how they combine. Partial compensation only.

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 computation: find the merchandise subtotal that funds shipping while retaining a target order contribution. That is a specific verb-plus-outcome rather than a restatement of the title, and the concept ('contribution floor') is distinct from the surrounding calculator siblings. It stops short of differentiating against any named alternative, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The scenario is implied: a seller reasoning about a free-shipping threshold versus margin. There is no explicit when-to-use, when-not-to-use, or reference to an alternative tool. For a self-contained read-only calculator that is tolerable, but the agent must infer the business context.

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.