Skip to main content
Glama

Payment Processor Fee Comparison

bpj_merchant_processor_fee_compare
Read-onlyIdempotent

Compare two processor quotes across successful payments using order value, percentage rates and per-transaction fees.

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": {
      "basket": "<basket>",
      "orders": "<orders>",
      "rateA": "<rateA>",
      "fixedA": "<fixedA>",
      "rateB": "<rateB>",
      "fixedB": "<fixedB>"
    },
    "name": "bpj_merchant_processor_fee_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateAYes
rateBYes
basketYes
fixedAYes
fixedBYes
ordersYes

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 declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds one real behavioral fact — the comparison covers successful payments only — but says nothing about what the result contains (per-processor totals, delta, winner) despite there being no output schema to fall back on.

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 nineteen-word sentence that front-loads the verb and resource with no filler. It is efficient, though the terseness leaves the exclusions and output implicitly unstated rather than deliberately summarised.

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 six-required-parameter tool with no output schema, the definition is minimally adequate: it identifies inputs conceptually and bounds the scope to successful payments. It stops short of describing the comparison result or the treatment of the orders multiplier, which is the main thing an agent cannot infer.

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%, but every property carries a self-explanatory title ('Processor A percentage (%)', 'Average paid order amount', 'Paid orders', 'fixed fee per transaction'). The description reinforces the rate and fixed-fee inputs and the order-value basis, but never explains the 'orders' parameter or that 'basket' is an average rather than a total.

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 a specific verb ('Compare') and a specific resource ('two processor quotes') along with the cost components being modelled. It is clearly a fee-comparison tool, distinguishable from generic siblings such as bpj_compare_json, though it never names the closest domain alternative (bpj_supplier_delivered_quote_comparison) to make the boundary explicit.

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 or when-not-to-use guidance and no named alternative. The only scope hint is 'across successful payments', which implies failed/refunded transactions are excluded, but an agent gets no help deciding between this and the other quote-comparison siblings.

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.