Skip to main content
Glama

Target Cost Incentive Sharing

bpj_incentive_contract_sharing
Read-onlyIdempotent

Adjust the target fee by the contractor’s share of cost underruns or overruns and apply the fee floor and ceiling.

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": {
      "targetCost": "<targetCost>",
      "reimbursable": "<reimbursable>",
      "targetFee": "<targetFee>",
      "share": "<share>",
      "minFee": "<minFee>",
      "maxFee": "<maxFee>"
    },
    "name": "bpj_incentive_contract_sharing"
  }
}

Input Schema

NameRequiredDescriptionDefault
shareYes
maxFeeYes
minFeeYes
targetFeeYes
targetCostYes
reimbursableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral content by disclosing that the result is clamped by a fee floor and ceiling, which is the tool's clamping behavior. It does not say which value is returned, whether the clamp is applied before or after sharing, or what happens when minFee > maxFee.

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 front-loaded sentence with no filler, and the mechanism is stated before the clamping caveat. It is efficient, though for a six-parameter required-everything calculation it is arguably too terse to be fully useful.

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?

Six required parameters, no output schema, and zero schema description coverage mean the description carries the full explanatory burden, yet it does not state the computation order, the sign convention for underrun vs overrun, or what the tool returns. It is not complete enough for an agent to call it correctly without guessing at the numeric semantics.

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% and the six parameters carry only terse titles ('Target fee', 'Allowable incurred cost'). The description maps loosely onto targetFee, share, and the floor/ceiling, but never explains the crucial relationship between targetCost and reimbursable (underrun = reimbursable < targetCost) that drives the adjustment, nor whether share is applied to the variance in currency or percent terms.

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?

States a specific verb (adjust) and resource (target fee) plus the mechanism (contractor's share of cost underruns/overruns). This distinguishes it from pure fee-cap tools like bpj_cost_plus_capped_fee, though the description never explicitly names or excludes any sibling.

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?

No when-to-use, prerequisites, or alternative guidance. The agent must infer from the title that this is the incentive-fee calculation step rather than, say, a validation or reporting tool. No exclusions are stated.

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.