Skip to main content
Glama

Cost Plus Capped Fee

bpj_cost_plus_capped_fee
Read-onlyIdempotent

Calculate a percentage fee on allowable costs, apply the fee ceiling and combine it with reimbursement.

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": {
      "reimbursable": "<reimbursable>",
      "fee": "<fee>",
      "feeCap": "<feeCap>"
    },
    "name": "bpj_cost_plus_capped_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
feeYes
feeCapYes
reimbursableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish that this is read-only, idempotent, closed-world, and non-destructive. The description adds useful behavioral detail about applying the fee percentage, enforcing the cap, and combining with reimbursement, but it does not disclose rounding, currency handling, or what is returned.

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 definition is a single front-loaded sentence with no filler. Each clause contributes to the calculation sequence: fee on costs, cap application, and reimbursement combination.

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 simple three-parameter calculation tool with annotations covering safety, the description covers the core operation. However, with no output schema, it should more clearly state the returned value or breakdown, and it omits rounding or currency conventions.

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 parameter meaning. It maps the three inputs reasonably well to allowable cost, fee percentage, and fee ceiling, and implies reimbursement is added back, but the exact formula and output composition remain slightly ambiguous.

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 calculation verb and resource: a percentage fee on allowable costs, a fee ceiling, and combining with reimbursement. It is clear what the tool computes, though it does not explicitly distinguish itself from nearby cost/fee calculation siblings.

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 guidance on when to use this tool versus alternatives such as fixed-fee or time-and-materials calculators. The description implies a cost-plus-capped-fee calculation but gives no exclusions, prerequisites, or routing advice.

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.