Skip to main content
Glama

Net Proceeds Gross-Up

bpj_net_proceeds_gross_up
Read-onlyIdempotent

Solve for the charge needed to net the target after a fixed payment fee and a percentage of the gross amount.

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": {
      "target": "<target>",
      "feeRate": "<feeRate>",
      "fee": "<fee>"
    },
    "name": "bpj_net_proceeds_gross_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
feeYes
targetYes
feeRateYes

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, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description adds the fee model (fixed fee plus a percentage of gross), which is genuinely useful behavior beyond the annotations. However, it says nothing about rounding/precision of the result, currency/units of the returned charge, or edge cases such as a feeRate near the declared 99.99 maximum.

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 well-formed sentence with the action verb 'Solve for' front-loaded and zero filler. The phrase 'net the target' is slightly dense jargon, but no sentence is wasted.

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 three-required-numeric-parameter calculator with no output schema, the description should convey the input/output relationship and any precision behavior. It conveys the gist (output = gross charge) but omits rounding, units, and the exact formula, so an agent could still misfill the rate as a fraction instead of a percent.

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%, though field titles ('Target net proceeds', 'Fixed charge per transaction', 'Percentage fee on gross charge (%)') carry basic meaning. The description loosely maps to all three inputs, but it does not pin down whether the rate is a percentage or fraction, nor give the exact relationship among target, fee, and gross charge, leaving the compensating work incomplete for a 0%-coverage schema.

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 specific computational task: solving for the gross charge that nets a target after a fixed fee plus a percentage of gross. That is far more informative than the title 'Net Proceeds Gross-Up', and it implicitly contrasts with the inverse retention tool. It stops short of naming any sibling or explicitly stating what the returned number is, so it is clear but not fully differentiated.

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?

Usage is only implied: the mention of 'a fixed payment fee and a percentage of the gross amount' signals a payment-fee gross-up scenario. There is no explicit statement of when to call this versus the sibling bpj_gross_net_retention or other fee-related calculators, and no prerequisites or exclusions are given.

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.