Skip to main content
Glama

Store Credit Tender Split

bpj_store_credit_tender_split
Read-onlyIdempotent

Apply store credit only to eligible merchandise and split the basket between redeemed credit and a cash tender.

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": {
      "subtotal": "<subtotal>",
      "eligible": "<eligible>",
      "credit": "<credit>"
    },
    "name": "bpj_store_credit_tender_split"
  }
}

Input Schema

NameRequiredDescriptionDefault
creditYes
eligibleYes
subtotalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, closed-world, and non-destructive behavior. The description adds the business rule that credit applies only to eligible merchandise and that the result is split into redeemed credit and cash tender, but it omits calculation details such as caps, rounding, or handling credit exceeding eligible value.

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?

The description is a single, front-loaded sentence with no redundant or filler wording.

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?

There is no output schema, so the description should explain the returned split and calculation rules. For a financial computation tool with three required numeric inputs, it leaves key behavior underspecified.

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 compensate. It references eligible merchandise, redeemed credit, and the basket, but does not define the three parameters (subtotal, eligible, credit), their units, or how they interact.

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 states a specific operation: applying store credit only to eligible merchandise and splitting the basket between redeemed credit and cash tender. The verb and resource are clear, though it does not explicitly differentiate itself from other credit or split tools.

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 description implies the context of store-credit tender splitting and states an eligibility restriction, but gives no explicit when-to-use guidance, prerequisites, or comparison to alternative credit/split tools.

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.