Skip to main content
Glama

Receivables Loss Allowance

bpj_receivables_loss_allowance
Read-onlyIdempotent

Apply separate loss rates to current and past-due receivables and determine the adjustment to the credit allowance.

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": {
      "current": "<current>",
      "overdue": "<overdue>",
      "currentLoss": "<currentLoss>",
      "overdueLoss": "<overdueLoss>",
      "allowance": "<allowance>"
    },
    "name": "bpj_receivables_loss_allowance"
  }
}

Input Schema

NameRequiredDescriptionDefault
currentYes
overdueYes
allowanceYes
currentLossYes
overdueLossYes

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?

The annotations already establish that this is a read-only, idempotent, non-destructive calculation, so the safety burden is reduced. The description adds useful behavioral information by saying the output is an adjustment to the credit allowance, but it does not disclose rounding, sign convention, or how the adjustment is derived.

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 redundant wording. Every clause contributes to the purpose and output description.

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 five-parameter calculation tool with no output schema, the description conveys the core computation and the nature of the result. It remains incomplete on output format, sign convention, and the precise role of the existing-allowance input.

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%, although parameter titles still identify current receivables, past-due receivables, existing allowance, and percentage loss rates. The description adds the mapping of separate rates to the two receivable buckets, but it does not explain how the existing allowance parameter is used in the adjustment or give formula-level detail.

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 uses a specific verb and resource: it applies separate loss rates to current and past-due receivables and determines the credit-allowance adjustment. That is clear enough to select the tool, but it does not distinguish it from a related sibling such as bpj_single_period_credit_loss.

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 explicit guidance on when to use this tool versus alternatives, nor any stated prerequisites or exclusions. The usage context is only implied by the calculation described.

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.